panic in AcpiExReleaseMutex
Moore, Robert
robert.moore at intel.com
Fri Dec 4 21:52:12 UTC 2009
Then I think you are stuck with figuring out why AcquiredMutexList is NULL.
AcquiredMutexList is set in AcpiExLinkMutex, clearing in AcpiExUnlinkMutex.
In AcpiExAcquireMutex, AcpiExLinkMutex is called after the mutex is successfully acquired, and only on the first acquisition.
In AcpiExReleaseMutexObject, AcpiExUnLinkMutex is called, but only if the Mutex OwnerThread ID is non-zero.
>-----Original Message-----
>From: Andriy Gapon [mailto:avg at freebsd.org]
>Sent: Friday, December 04, 2009 1:45 PM
>To: Moore, Robert
>Cc: freebsd-acpi at freebsd.org; Tarick
>Subject: Re: panic in AcpiExReleaseMutex
>
>on 04/12/2009 23:38 Andriy Gapon said the following:
>> on 04/12/2009 23:24 Moore, Robert said the following:
>>> Another question, however: is the global lock involved in any way?
>>
>> Yes. EC querying is performed under global lock. That is, it gets
>locked and
>> unlocked in EcGpeQueryHandler function before _Qxx evaluation.
>> I am actually curious why you asked this question.
>
>Hmm, I lied, this is done only if _GLK successfully evaluates to non-zero
>value,
>which is not the case.
>
>--
>Andriy Gapon
More information about the freebsd-acpi
mailing list