From owner-acpi-jp@jp.FreeBSD.org Tue Jan 29 10:26:43 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g0T1Qhn09520;
	Tue, 29 Jan 2002 10:26:43 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g0T1Qh609515
	for <acpi-jp@jp.freebsd.org>; Tue, 29 Jan 2002 10:26:43 +0900 (JST)
	(envelope-from dwhite@resnet.uoregon.edu)
Received: from localhost (dwhite@localhost)
	by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g0T1R9N12757
	for <acpi-jp@jp.freebsd.org>; Mon, 28 Jan 2002 17:27:10 -0800 (PST)
Date: Mon, 28 Jan 2002 17:27:09 -0800 (PST)
From: Doug White <dwhite@resnet.uoregon.edu>
To: acpi-jp@jp.FreeBSD.org
Message-ID: <20020128171709.O6367-100000@resnet.uoregon.edu>
X-All-Your-Base: are belong to us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+011218
X-Sequence: acpi-jp 1565
Subject: [acpi-jp 1565] Problems with HP Omnibook 6000
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: dwhite@resnet.uoregon.edu

Hello,

I'm trying to debug ACPI on an HP Omnibook 6000. With the default
settings, the machine reboots just after the acpi message appears on
5.0-CURRENT.

I've done a couple of weekends of debugging and have isolated the
problematic ACPI method(s). It appears to be related to the _CRS resource
methods for the system busses _SB_.PCI0 and the CardBus controllers at
_SB_.PCI0.FDS_.FCB[12] and the interrupt routing on _SB_.LNK[A-D].
Putting these into 'debug.acpi.avoid' gets the system up, with CPU speed
control and thermal zone control available. Configuring the debugger to
halt before enabling devices and running _SB_.PCI0._CSR manually results
in the immediate reboot.

Turning on heavy debugging finds the ACPI code recursing 175+ functions
deep, and one panic I got produced a 211 line backtrace. (unfortunately
the machine can't take crashdumps due to a disk config fault.)  So I think
it may be blowing out the kernel stack or getting stuck in some sort of
infinite recursion. The same set of functions, about 25 or 26 levels or
so, appeared 9 times. (thanks to scrollback for the rough calculations)
This is quite repeatable.

I'm interested in next steps for debugging this system.  The DSDT is
available at http://people.freebsd.org/~dwhite/hp6000/hp.dsdt for your
perusal, and a acpidump'd ASL version is in acpidump.txt.  I have a couple
of debugging session traces that may or may not be useful in that
directory as well.

This laptop is company property but I have full control over it and the
FreeBSD install on it is available for debugging.

Thanks for any assistance!

Doug White                    |  FreeBSD: The Power to Serve
dwhite@resnet.uoregon.edu     |  www.FreeBSD.org

