On 01-Mar-02 David Wolfskill wrote:
>>Date: Fri, 01 Mar 2002 10:47:09 +0900
>>From: Jun Kuriyama <[EMAIL PROTECTED]>
>>At Fri, 1 Mar 2002 01:34:17 +0000 (UTC),
>>John Baldwin wrote:
>>> That's bad juju panic. :)  Are you using witness?  If so, did you get a
>>> printf
>>> about sleeping with a lock held?
>>I think I did not get lock warning just before this assertion
>>failure.  But on my environment, I got this lock order reversal
>>everytime I booted.
>>lock order reversal
>> 1st 0xc036afc0 allproc @ ../../../kern/vfs_syscalls.c:452
>> 2nd 0xc7ecce34 filedesc structure @ ../../../kern/vfs_syscalls.c:457
> Although I did not get the reported panic, I have also had a very
> similar lock order reversal reported since (at least) the -CURRENT of
> 22 Feb. (which as far back as I presently keep the message log).
> I'm skeptical that there is a significant relationship between the panic
> & the lock order reversal.

There's not.  The panic is due to some process being asleep or something while
holding a mutex.  That reversal is a known problem that involves redoing select
a bit.


John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to