From owner-freebsd-acpi@FreeBSD.ORG  Thu Mar 17 00:32:32 2011
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@FreeBSD.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 16293106566B;
	Thu, 17 Mar 2011 00:32:32 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: freebsd-acpi@FreeBSD.org
Date: Wed, 16 Mar 2011 20:32:22 -0400
User-Agent: KMail/1.6.2
References: <20110316115254.59f8b6f7@heavennet.ru>
	<201103161822.40131.jkim@FreeBSD.org>
	<4911F71203A09E4D9981D27F9D830858CAD03779@orsmsx503.amr.corp.intel.com>
In-Reply-To: <4911F71203A09E4D9981D27F9D830858CAD03779@orsmsx503.amr.corp.intel.com>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201103162032.23801.jkim@FreeBSD.org>
Cc: "Ilya A. Arhipov" <micro@heavennet.ru>, "Moore,
	Robert" <robert.moore@intel.com>, Andriy Gapon <avg@freebsd.org>
Subject: Re: Panic after update kernel
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2011 00:32:32 -0000

On Wednesday 16 March 2011 07:49 pm, Moore, Robert wrote:
> The latest version of acpica released today (20110316) should fix
> this issue for you.

Cool!

I just committed it on HEAD now.  Please try it and let us know.

Thanks!

Jung-uk Kim

> Bob
>
> >-----Original Message-----
> >From: Jung-uk Kim [mailto:jkim@FreeBSD.org]
> >Sent: Wednesday, March 16, 2011 3:22 PM
> >To: Andriy Gapon
> >Cc: Ilya A. Arhipov; Moore, Robert; freebsd-acpi@freebsd.org
> >Subject: Re: Panic after update kernel
> >
> >On Wednesday 16 March 2011 11:12 am, Andriy Gapon wrote:
> >> on 16/03/2011 16:18 Ilya A. Arhipov said the following:
> >> > 2011/3/16 Andriy Gapon <avg@freebsd.org
> >> > <mailto:avg@freebsd.org>>
> >> >
> >> >     on 16/03/2011 10:52 Ilya A. Archipov said the following:
> >> >     > and see:
> >> >     > http://imm.io/4nzZ
> >> >     >
> >> >     > what information still needs to provide?
> >> >
> >> >     'bt' command output please (a screenshot is fine).
> >> >
> >> >     --
> >> >     Andriy Gapon
> >> >
> >> >
> >> > boot:
> >> > http://imm.io/4nTZ
> >> > bt:
> >> > http://imm.io/4nTS <-first
> >> > http://imm.io/4nUd <-last
> >>
> >> So the panic is that we acquire a regular (non-spin) mutex in an
> >> interrupt context. Not sure if this is a FreeBSD issue
> >> (implementation of ACPI semaphore) or some ACPICA issue (e.g.
> >> doing something wrong in an interrupt handler).
> >>
> >> Jung-uk, Robert, can you please take a look?
> >
> >_GL_ creates a semaphore and this semaphore is exclusively used in
> >interrupt context.  Also, it is always used to wait forever if it
> >cannot acquire the necessary global lock.  This is really bad for
> > us because a semaphore requires a lock object to prevent sleeping
> > forever without being waken up.  Only workaround I can think of
> > is to turn AcpiOsWaitSemaphore() & AcpiOsSignalSemaphore() into
> > tsleep(9) & wakeup(9) because that's exactly what it wants to do,
> > it seems.
> >
> >JK
>
> _______________________________________________
> freebsd-acpi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
> To unsubscribe, send any mail to
> "freebsd-acpi-unsubscribe@freebsd.org"