From owner-freebsd-mobile Mon Jan 8 15: 1:29 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 7D0C737B6A3 for ; Mon, 8 Jan 2001 15:01:09 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f08Mx7G49657; Mon, 8 Jan 2001 14:59:07 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200101080514.f085E5s41362@harmony.village.org> Date: Mon, 08 Jan 2001 15:01:08 -0800 (PST) From: John Baldwin To: Warner Losh Subject: RE: Report Cc: mobile@FreeBSD.org Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 08-Jan-01 Warner Losh wrote: > Giant lock is held by someone else when we go into our loop, so we > can't go into it at all. Or thus it would appear. I don't know how > to check for things like this. I get the interrupt just fine, but the > thread never runs. I haven't looked into this issue at all. So for > my laptop eject fails a horrible death on eject. Giant is special. It is released in tsleep() and any other time that a process calls mi_switch() except for when it is blocking on acquiring another sleep mutex, so when your thread gets scheduled and run it will be able to get Giant w/o a problem. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message