From owner-acpi-jp@jp.FreeBSD.org Sat Oct 26 04:03:10 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g9PJ3AL77320;
	Sat, 26 Oct 2002 04:03:10 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from rootlabs.com (root.org [67.118.192.226])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with SMTP/inet id g9PJ35377297
	for <acpi-jp@jp.freebsd.org>; Sat, 26 Oct 2002 04:03:08 +0900 (JST)
	(envelope-from nate@rootlabs.com)
Received: (qmail 73183 invoked by uid 1000); 25 Oct 2002 19:02:59 -0000
From: Nate Lawson <nate@root.org>
To: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
cc: current@freebsd.org, acpi-jp@jp.FreeBSD.org
In-Reply-To: <20021005.100416.13778160.iwasaki@jp.FreeBSD.org>
Message-ID: <Pine.BSF.4.21.0210051948290.2736-100000@root.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Fri, 25 Oct 2002 12:02:59 -0700
X-Sequence: acpi-jp 1911
Subject: [acpi-jp 1911] Re: ACPI errors and then panic
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: nate@root.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021018

Thank you for the reply.

On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote:
> Hi,
> # ACPI CA related problem should be sent to acpi-jp@jp.freebsd.org
> # so that Intel folks can be aware of the problem.

Ok, I didn't know that.
 
> From: Nate Lawson <nate@root.org>
> Subject: ACPI errors and then panic
> Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT)
> Message-ID: <Pine.BSF.4.21.0210041705180.96157-100000@root.org>
> 
> > My laptop appears to work ok without ACPI but of course I don't get
> > suspend, resume, etc.  I have never been able to get ACPI to work with it,
> > including with a -current as of 2 hours ago.  If ACPI is enabled, I get a
> > spew of:
> > 
> > ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name
> > 
> > and then a panic from acpi_attach.
> 
> First several lines of DDB backtrace would be very helpful
> to track the problem down.
> Also having following lines in your loader.conf would be
> helpful to determine which object causes the ACPI CA Eroor.
> 
> debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_BUS"
> debug.acpi.level="ACPI_LV_WARN ACPI_LV_ERROR ACPI_LV_OBJECTS"

I have placed a ddb session with tracebacks for two panics at:
  http://www.root.org/~nate/acpi/ddb1
  http://www.root.org/~nate/acpi/ddb2

I set your debug options in device.hints.
 
One interesting thing is that the oem sysctl node seems bogus:
   hint.acpi.0.oem=IBM   ??????
where the ?'s are invalid characters like the happy face.

> BTW, what's model name?  Some ThinkPad's are blacklisted such as
> IBM 600E.  And may I add your ACPI data to our repo. (in Japan) ?

IBM T23.  Feel free to use the dsdt and/or asl however you wish.

> > Here are the appropriate files...
> >   http://www.root.org/~nate/acpi/ibm.asl
> >   http://www.root.org/~nate/acpi/ibm.dsdt
> >   http://www.root.org/~nate/acpi/ibm.dmesg  (from a working boot)

(Note that I renamed the .aml file to asl as shown above)

-Nate



