On Tue, Mar 02, 1999 at 06:16:50PM -0500, Brian Feldman wrote: > > Where exactly does thrd_sleep come in, since that's where the program locks > up now? Can't be killed, of course... >
The lock manager isn't bright enough to detect that the process already holds a read lock when it attempts to get the write lock. Thus, you get the "thrd_sleep" instead of a panic. In short, same bug, different symptoms. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
