From owner-freebsd-current Wed May 16 9:49:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 55CE537B422 for ; Wed, 16 May 2001 09:49:46 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f4GGn5G70354; Wed, 16 May 2001 09:49:09 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 16 May 2001 09:48:12 -0700 (PDT) From: John Baldwin To: Bob Bishop Subject: RE: panic: sleeping process owns a mutex Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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