[issue547] 1.8 release cd ACPI message loop

YONETANI Tomokazu qhwt+dfly at les.ath.cx
Sun Jul 8 22:15:55 PDT 2007


On Sun, Jun 03, 2007 at 08:54:20PM -0000, Justin C. Sherrill wrote:
> Tested this with a 1.9 CD from yesterday, with debug.acpi_semaphore_debug set:
> 
> AcpiOsWaitSemaphore: Acquire 1, units 0, pending 0, sem 0xc1080b28, thread 1
> AcpiOsWaitSemaphore: Sleep 1000, pending 1, semaphore 0xc1080b28, thread 1
> AcpiOsWaitSemaphore: Timeout 1000, pending 0, semaphore 0xc1080b28
> ACPI Exception (evregion-0529): AE_TIME, Returned by Handler for
> [EmbeddedControl] [20061109]
> AcpiOsSignalSemaphore: Release 1, units 1, pending 0, semaphore 0xc1080b28, thread 1
> ACPI Error (psparse-0638): Method parse/execution failed
> [\_SB_.PCI0.ISA0.EC0_.I2RB] (Node 0xc1084e78), AE_TIME
> ACPI Error (psparse-0638): Method parse/execution failed
> [\_SB_.PCI0.ISA0.EC0_.UPDT] (Node 0xc1084dd0), AE_TIME
> ACPI Error (psparse-0638): Method parse/execution failed [\_TZ_.THM0._TMP]
> (Node 0xc1084a10), AE_TIME

I uploaded an ISO image built from yesterday's source code
on my leaf account, with ACPI_DEBUG=yes defined:
  http://leaf.dragonflybsd.org/~y0netan1/dfly-20070708.iso.bz2
Please drop into boot loader, and type following commands:
  set debug.acpi.layer=ACPI_OS_SERVICES
  set debug.acpi.level=ACPI_LV_MUTEX
This should enable some more debugging messages which may be useful.

Besides that, can you send me the acpidump output on your computer?

> I do notice early on a number of ACPI messages about "cannot release global
> lock" - they scroll by fast enough I haven't been able to capture them.  Setting 
> debug.acpi.disabled="thermal" (or "ec") gave a slightly new set of errors, which
> I can write out if they're important.

I'd like to know whether setting debug.acpi.disabled="thermal" (or "ec")
fixes the first (looping) message?

Cheers.





More information about the Bugs mailing list