From owner-freebsd-current@FreeBSD.ORG  Fri Nov 28 01:39:29 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0626116A4CE
	for <current@FreeBSD.org>; Fri, 28 Nov 2003 01:39:29 -0800 (PST)
Received: from email05.aon.at (WARSL402PIP4.highway.telekom.at [195.3.96.79])
	by mx1.FreeBSD.org (Postfix) with SMTP id A1C3143F3F
	for <current@FreeBSD.org>; Fri, 28 Nov 2003 01:39:27 -0800 (PST)
	(envelope-from shoesoft@gmx.net)
Received: (qmail 488600 invoked from network); 28 Nov 2003 09:39:26 -0000
Received: from m126p027.dipool.highway.telekom.at (HELO ?62.46.5.187?)
	([62.46.5.187]) (envelope-sender <shoesoft@gmx.net>)
	by qmail5rs.highway.telekom.at (qmail-ldap-1.03) with SMTP
	for <shoesoft@gmx.net>; 28 Nov 2003 09:39:26 -0000
From: Stefan Ehmann <shoesoft@gmx.net>
To: Stefan Ehmann <shoesoft@gmx.net>
In-Reply-To: <1070011860.777.5.camel@shoeserv.freebsd>
References: <200311280002.hAS029eF016292@gw.catspoiler.org>
	 <1070011860.777.5.camel@shoeserv.freebsd>
Content-Type: text/plain
Message-Id: <1070012366.871.1.camel@shoeserv.freebsd>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Fri, 28 Nov 2003 10:39:27 +0100
Content-Transfer-Encoding: 7bit
cc: current@FreeBSD.org
Subject: Re: panic on 5.2 BETA: blockable sleep lock
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Nov 2003 09:39:29 -0000

On Fri, 2003-11-28 at 10:31, Stefan Ehmann wrote:
> On Fri, 2003-11-28 at 01:02, Don Lewis wrote:
> > On 27 Nov, Stefan Ehmann wrote:
> > > On Wed, 2003-11-26 at 08:33, Don Lewis wrote:
> > >> The problem is that selrecord() wants to lock a MTX_DEF mutex, which can
> > >> cause a context switch if the mutex is already locked by another thread.
> > >> This is contrary to what bktr_poll() wants to accomplish by calling
> > >> critical_enter().
> > > 
> > > Strange enough that does not seem to happen with a kernel built without
> > > INVARIANTS and WITNESS. Does this make any sense or is this just by
> > > chance?
> > 
> > You might try the patch below with WITNESS enabled.  I don't have the
> > hardware, so I can't test it.  It compiles for me, but for all I know it
> > could delete all your files if you run it.
> 
> Unfortunately, after running the patched kernel some time I got a
> slightly different panic:

Please ignore the message above - this was the panic from an unpatched
kernel - I was debugging the wrong core.

Thanks again for quick help.