Date: Wed, 16 May 2001 09:55:40 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: John Baldwin <jhb@FreeBSD.ORG> Cc: Bob Bishop <rb@gid.co.uk>, current@FreeBSD.ORG Subject: RE: panic: sleeping process owns a mutex Message-ID: <Pine.BSF.4.21.0105160955120.8660-100000@beppo.feral.com> In-Reply-To: <XFMail.010516094812.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Oh, I'd like you to think twice about this. Massive amounts of driver rototilling should be avoided at this point. On Wed, 16 May 2001, John Baldwin wrote: > > On 16-May-01 Bob Bishop wrote: > > Hi, > > > > This while building world, with a kernel cvsup at Fri Apr 27 04:06:40 BST > > 2001 > > > > kern/kern_synch.c:386 sleeping with "vr0" locked from pci/if_vr.c:1315 > > > > abridged backtrace: > > > > panic() > > propagate_priority() > > _mtx_lock_sleep() > > vr_intr() > > ithread_loop() > > fork_exit() > > fork_trampoline() > > Well, I think the best thing to do for now will be to back out all the ethernet > driver locking until we figure out how we are actually going to lock them. > The original locks that went in starting with fxp many months ago weren't quite > right but have been mostly harmless up to this point. There are some cases > where we sleep with locks however, which can lead to problems. > > -- > > 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-current" in the body of the message > 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?Pine.BSF.4.21.0105160955120.8660-100000>