HP LH3000r hangs on boot with ACPI enabled

John Baldwin jhb at freebsd.org
Tue Feb 20 18:20:45 UTC 2007


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


More information about the freebsd-acpi mailing list