From owner-freebsd-acpi@FreeBSD.ORG  Fri Mar  1 21:24:03 2013
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 90FBBD47
 for <freebsd-acpi@freebsd.org>; Fri,  1 Mar 2013 21:24:03 +0000 (UTC)
 (envelope-from jkim@FreeBSD.org)
Received: from hammer.pct.niksun.com (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 by mx1.freebsd.org (Postfix) with ESMTP id 3A7971875;
 Fri,  1 Mar 2013 21:24:03 +0000 (UTC)
Message-ID: <51311BF8.8060602@FreeBSD.org>
Date: Fri, 01 Mar 2013 16:22:00 -0500
From: Jung-uk Kim <jkim@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130220 Thunderbird/17.0.3
MIME-Version: 1.0
To: Hans Petter Selasky <hps@bitfrost.no>
Subject: Re: ACPI locking bugs?
References: <201302271453.43985.hps@bitfrost.no> <512E5E4C.807@FreeBSD.org>
 <6951816.YIytQN410a@laptop015.hselasky.homeunix.org>
In-Reply-To: <6951816.YIytQN410a@laptop015.hselasky.homeunix.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: freebsd-acpi@freebsd.org
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Fri, 01 Mar 2013 21:24:03 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-03-01 02:52:12 -0500, Hans Petter Selasky wrote:
> The problem is not locking or locking order, but that the locking
> wait for signals. You know when you have a thread, you kan kill it
> using a signal. I think at shutdown all threads and processes gets
> a KILL signal, and that confuses ACPICA if it is about to grab a
> mutex.

Hmm...  That's an interesting thought.  It can happen if a thread gets
killed while holding a ACPI mutex/semaphore.  However, I am not sure
how to fix that situation.  With or without PCATCH, it can happen
anyway. :-(

Jung-uk Kim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBAgAGBQJRMRv4AAoJECXpabHZMqHOG/EH/3JBUZrkTpybpD6IfdtK5zHP
qsTz4YQ0tX5JQUs2mWVdg24fINJ8pRMTKll5WpwHA6qB9lgzVyMFWTNZKwJ/dbLs
HY9O1qkYem5a9H7rqU5E8Z1tKUeVlzyQFt7aTuIRbeHAYNseDi1qWZfesNHXk8yD
zqSqnMNv0+9a39ct8BLoRBTNa3jaRMrlqf7Ks1skph4e6kQExtoEG5e+rjq39Oiv
HZiJbMqcVos+xhDc921NOGgQtHH++aLkhMvimrOhPAnTD/7iNU4uFuSQ5nxeQoDS
G6vwJJqMDeHdBdZzW398RIUbJNHQcUJTiLT1U7VQx2QIXhUKNMuKIREQJQwI8rY=
=4qjW
-----END PGP SIGNATURE-----