From owner-freebsd-acpi@FreeBSD.ORG Fri Dec 4 21:08:49 2009 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 758AE1065672 for ; Fri, 4 Dec 2009 21:08:49 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mx1.freebsd.org (Postfix) with ESMTP id 370E98FC17 for ; Fri, 4 Dec 2009 21:08:48 +0000 (UTC) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 04 Dec 2009 13:08:13 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.47,344,1257148800"; d="scan'208";a="575772004" Received: from orsmsx602.amr.corp.intel.com ([10.22.226.211]) by orsmga001.jf.intel.com with ESMTP; 04 Dec 2009 13:08:34 -0800 Received: from orsmsx503.amr.corp.intel.com ([10.22.226.47]) by orsmsx602.amr.corp.intel.com ([10.22.226.211]) with mapi; Fri, 4 Dec 2009 13:08:48 -0800 From: "Moore, Robert" To: Andriy Gapon Date: Fri, 4 Dec 2009 13:08:46 -0800 Thread-Topic: panic in AcpiExReleaseMutex Thread-Index: Acp1I3OygVYgasCbQLaTpWo+B3vr2gAAPAxwAABVVtA= Message-ID: <4911F71203A09E4D9981D27F9D8308583E8F2BC7@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> <4B1975EE.5070803@icyb.net.ua> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-acpi@freebsd.org" , Tarick Subject: RE: panic in AcpiExReleaseMutex X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2009 21:08:49 -0000 >Now, we have a code in EcSpaceHandler that makes a >direct call to EcGpeQueryHandler during a cold boot phase if SCI bit is se= t >in >CSR register. EcGpeQueryHandler performs an EC query and executes _Qxx >method if need. OK, I see. No GPE, but a direct call to the handler, which makes a query an= d invokes _Q20 or _Q09 What is the thread_id, and does it ever change for this thread? >-----Original Message----- >From: Moore, Robert >Sent: Friday, December 04, 2009 1:00 PM >To: 'Andriy Gapon' >Cc: freebsd-acpi@freebsd.org; Tarick >Subject: RE: panic in AcpiExReleaseMutex > >It would appear that a GPE is taken, for the EC device, thus invoking >EcGpeQueryHandler. In what context is _Q20 or _Q09 executed? > >This might be an important question: What is the thread_id of this initial >thread? > > > >>-----Original Message----- >>From: Andriy Gapon [mailto:avg@icyb.net.ua] >>Sent: Friday, December 04, 2009 12:50 PM >>To: Moore, Robert >>Cc: freebsd-acpi@freebsd.org; Tarick >>Subject: Re: panic in AcpiExReleaseMutex >> >>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 i= f >>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, n= o >>other >>threads are started yet. >> >> >>-- >>Andriy Gapon