>> osl-0854 [545] os_wait_semaphore : Failed to acquire >> semaphore[e3fce660|1|100], AE_TIME
> Probably an EC issue. Do you still see this with the latest > ACPI patch or mm tree (which includes EC interrupt mode). I just tried 2.6.16-rc1 + acpi-release-20060113-2.6.16-rc1.diff. That gets rid of the os_wait_semaphore messages, but acpi still hangs for about 10 seconds and then reports information only for battery 2. As a side benefit, 2.6.16-rc1 + acpi-release-20060113-2.6.16-rc1.diff fixed the general problem of "os_wait_semaphore : Failed to acquire semaphore" messages. See my report at <http://bugzilla.kernel.org/show_bug.cgi?id=5008> and the C program that could reliably generate them again. [Bug #5008 was eventually marked 'closed', but that's after the discussion diverged to a related topic: why 'acpi' was so slow, and that problem did improve with 2.6.15.] I tried the C program with 2.6.15 and it immediately generated many os_wait_semaphore messages. I rebooted into the 2.6.16-rc1+acpi-20060113 and the C program didn't generate any messages. -Sanjoy `Never underestimate the evil of which men of power are capable.' --Bertrand Russell, _War Crimes in Vietnam_, chapter 1. - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
