Date: Fri, 01 Mar 2013 16:22:00 -0500 From: Jung-uk Kim <jkim@FreeBSD.org> To: Hans Petter Selasky <hps@bitfrost.no> Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI locking bugs? Message-ID: <51311BF8.8060602@FreeBSD.org> In-Reply-To: <6951816.YIytQN410a@laptop015.hselasky.homeunix.org> References: <201302271453.43985.hps@bitfrost.no> <512E5E4C.807@FreeBSD.org> <6951816.YIytQN410a@laptop015.hselasky.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51311BF8.8060602>