Edward O'Callaghan <[email protected]> added the comment: The problem is with the AML Mutex handling function AcpiExReleaseMutex where the function can fault under the very rare condition when the interpreter has blocked, the interpreter lock is released, the interpreter is then reentered via the same thread, and attempts to acquire an AML mutex that was previously acquired.
This is indeed fixed in the acpica-unix-20100806 snapshot. ---------- status: unread -> chatting _____________________________________________________ DragonFly issue tracker <[email protected]> <http://bugs.dragonflybsd.org/issue1846> _____________________________________________________
