Date: Mon, 08 Jan 2001 15:01:08 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Warner Losh <imp@harmony.village.org> Cc: mobile@FreeBSD.org Subject: RE: Report Message-ID: <XFMail.010108150108.jhb@FreeBSD.org> In-Reply-To: <200101080514.f085E5s41362@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010108150108.jhb>