Date: Thu, 28 Feb 2002 17:53:56 -0800 (PST) From: David Wolfskill <david@catwhisker.org> To: jhb@FreeBSD.ORG, kuriyama@imgsrc.co.jp Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Assertion faild at kern_mutex.c Message-ID: <200203010153.g211ruo05300@bunrab.catwhisker.org> In-Reply-To: <7m664h12le.wl@waterblue.imgsrc.co.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
>Date: Fri, 01 Mar 2002 10:47:09 +0900 >From: Jun Kuriyama <kuriyama@imgsrc.co.jp> >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. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203010153.g211ruo05300>