From owner-freebsd-current Wed May 16 9:55:44 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D547437B423; Wed, 16 May 2001 09:55:40 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id JAA13975; Wed, 16 May 2001 09:55:40 -0700 Date: Wed, 16 May 2001 09:55:40 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: Bob Bishop , current@FreeBSD.ORG Subject: RE: panic: sleeping process owns a mutex In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -- 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