Date: Fri, 04 Dec 2009 22:49:50 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: "Moore, Robert" <robert.moore@intel.com> Cc: "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>, Tarick <tungan@ukr.net> Subject: Re: panic in AcpiExReleaseMutex Message-ID: <4B1975EE.5070803@icyb.net.ua> In-Reply-To: <4911F71203A09E4D9981D27F9D8308583E8F2A1F@orsmsx503.amr.corp.intel.com> References: <4B178387.4050601@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308583E8F26CF@orsmsx503.amr.corp.intel.com> <4B189CD6.30906@icyb.net.ua> <4911F71203A09E4D9981D27F9D8308583E8F2A1F@orsmsx503.amr.corp.intel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
on 04/12/2009 20:45 Moore, Robert said the following: > Yes, you are correct. I did not have the code in front of me at the time. > > When AcpiExReleaseMutex is called, apparently the mutex is in fact held, > otherwise the function would have aborted immediately. > > When the mutex is held, the Thread->AcquiredMutexList is expected to hold (at > the minimum) the mutex object being released. Something is very wrong if this > list is NULL when releasing the mutex. > > Just to make sure: All of this is happening in the same thread? Yes, this happens when there is only the initial thread running on BSP, no other threads are started yet. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B1975EE.5070803>