From owner-freebsd-current Sun Jun 27 1:55: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id DA54B14C96 for ; Sun, 27 Jun 1999 01:55:02 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA25097; Sun, 27 Jun 1999 10:54:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Peter Wemm Cc: Matthew Dillon , current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: BUF_LOCK() related panic.. In-reply-to: Your message of "Sun, 27 Jun 1999 16:44:14 +0800." <19990627084414.24D4D81@overcee.netplex.com.au> Date: Sun, 27 Jun 1999 10:54:02 +0200 Message-ID: <25095.930473642@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990627084414.24D4D81@overcee.netplex.com.au>, Peter Wemm writes: >Speaking of SMP and simple locks, I'd like to turn on the debugging >simplelocks that keep a reference count and check before switching to make >sure that a process doesn't sleep holding a lock. This is a pretty >fundamental sanity check and would have found the LK_INTERLOCK problem >above before it got committed. Absolutely, I also have seen some indications that checking spl levels (#ifdef DIAGNOSTIC) might be warranted. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message