From owner-freebsd-acpi@FreeBSD.ORG Mon Feb 19 21:04:57 2007 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A620216D633 for ; Mon, 19 Feb 2007 21:04:57 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from misav06.sasknet.sk.ca (misav06.sasknet.sk.ca [142.165.20.170]) by mx1.freebsd.org (Postfix) with ESMTP id 5C25313C441 for ; Mon, 19 Feb 2007 21:04:57 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from bgmpomr1.sasknet.sk.ca ([142.165.72.22]) by misav06 with InterScan Messaging Security Suite; Mon, 19 Feb 2007 15:04:53 -0600 Received: from [192.168.1.64] (adsl-75-51-73-22.dsl.lsan03.sbcglobal.net [75.51.73.22]) by bgmpomr1.sasknet.sk.ca (SaskTel eMessaging Service) with ESMTPA id <0JDQ0056KAK48100@bgmpomr1.sasknet.sk.ca>; Mon, 19 Feb 2007 15:04:53 -0600 (CST) Date: Mon, 19 Feb 2007 13:04:02 -0800 From: Stephen Hurd In-reply-to: <200702191051.18369.jhb@freebsd.org> To: John Baldwin Message-id: <45DA10C2.1070004@sasktel.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT References: <45D559E9.9060806@sasktel.net> <200702191051.18369.jhb@freebsd.org> User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.2pre) Gecko/20070208 SeaMonkey/1.1 Cc: freebsd-acpi@freebsd.org Subject: Re: HP LH3000r hangs on boot with ACPI enabled X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Feb 2007 21:04:57 -0000 John Baldwin wrote: > On Friday 16 February 2007 02:14, Stephen Hurd wrote: > >> System does not complete the boot (hang) with ACPI enabled using FreeBSD >> 6.2-RELEASE >> > > I would look for a BIOS update. Yeah, that was the first thing I did... BIOS is newest available. > First of all this message is worrying: > > >> ACPI-0347: *** Error: During resolve, Unknown Reference opcode 2D >> (AE_NOT_CONFIGURED) in 0xc3c5d600 >> ACPI-1304: *** Error: Method execution failed [\_SB_.PCI0.ISA_.LINK] >> (Node 0xc3bcdbc0), AE_AML_INTERNAL >> ACPI-1304: *** Error: Method execution failed [\_SB_.PCI0.INIT] >> (Node 0xc3b78480), AE_AML_INTERNAL >> ACPI-1304: *** Error: Method execution failed [\_SB_.PCI0._INI] >> (Node 0xc3b78500), AE_AML_INTERNAL >> > > This means it wasn't able to finish the init method for the PCI bus. > Secondly, if you compare the IRQs for the two dmesg's (which you can in > this case), you will see that ACPI uses different (and in theory, wrong) > IRQs for the sym0, sym1, and ahc0 devices, and the last one is causing > your hang I think. > Yeah. To me it seems to imply that support for the 0x2D opcode is missing from FreeBSD... when I recompile the aml (I get a _WAK returns no value warning) and use that, the error is still the same. To me, that implies that the compiler supports it, but the AML interpreter doesn't (of course, I know zip about AML, ASL, and ACPI, so my opinion is worthless.)