[issue547] 1.8 release cd ACPI message loop

Justin C. Sherrill bugs at crater.dragonflybsd.org
Sun Jun 3 13:55:08 PDT 2007


Justin C. Sherrill <justin at shiningsilence.com> added the comment:

(Resurrecting ancient issue)  

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 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.

_____________________________________________________
DragonFly issue tracker <bugs at lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue547>
_____________________________________________________






More information about the Bugs mailing list