From owner-freebsd-acpi@FreeBSD.ORG Wed Feb 21 03:25:32 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 C5AC016AEED for ; Wed, 21 Feb 2007 03:25:32 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 2B27613C48E for ; Wed, 21 Feb 2007 03:25:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l1L3POCx089842; Tue, 20 Feb 2007 22:25:27 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Moore, Robert" Date: Tue, 20 Feb 2007 22:25:11 -0500 User-Agent: KMail/1.9.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702202225.11678.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Tue, 20 Feb 2007 22:25:28 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2614/Tue Feb 20 13:53:11 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org, Stephen Hurd 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: Wed, 21 Feb 2007 03:25:32 -0000 On Tuesday 20 February 2007 18:52, Moore, Robert wrote: > We have seen things like this when the BIOS incorrectly fusses with the > raw AML. > > Please post the acpidump for this machine. It was earlier in the thread: http://nix.synchro.net/hp-lh3000r.asl > > -----Original Message----- > > From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > > acpi@freebsd.org] On Behalf Of John Baldwin > > Sent: Tuesday, February 20, 2007 9:27 AM > > To: Stephen Hurd > > Cc: freebsd-acpi@freebsd.org > > Subject: Re: HP LH3000r hangs on boot with ACPI enabled > > > > On Monday 19 February 2007 16:04, Stephen Hurd wrote: > > > 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.) > > > > The interpreter we have is the ACPI-CA one from Intel that Linux uses. > > Supporting the opcode isn't going to magically fix the flat-wrong > Global > > System Interrupt numbers in the _PRT tables though. :) > > > > -- > > John Baldwin > > _______________________________________________ > > freebsd-acpi@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > > To unsubscribe, send any mail to > "freebsd-acpi-unsubscribe@freebsd.org" > -- John Baldwin