From owner-freebsd-current@FreeBSD.ORG  Tue Apr 15 03:50:39 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 6751537B401; Tue, 15 Apr 2003 03:50:39 -0700 (PDT)
Received: from mx0.freebsd-services.com (survey.codeburst.net
	[195.149.39.161])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 76D4943FAF; Tue, 15 Apr 2003 03:50:34 -0700 (PDT)
	(envelope-from paul@freebsd-services.com)
Received: by mx0.freebsd-services.com (Postfix, from userid 1002)
	id 1E55B1B219; Tue, 15 Apr 2003 11:50:33 +0100 (BST)
Date: Tue, 15 Apr 2003 11:50:32 +0100
From: Paul Richards <paul@freebsd-services.com>
To: Pawel Worach <pawel.worach@telia.com>
Message-ID: <20030415105032.GB93652@survey.codeburst.net>
References: <XFMail.20030414155909.jhb@FreeBSD.org>
	<000201c302c1$e0d1dee0$1401a8c0@corona>
	<20030414223318.GA75035@survey.codeburst.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030414223318.GA75035@survey.codeburst.net>
User-Agent: Mutt/1.4.1i
cc: current@FreeBSD.org
cc: 'John Baldwin' <jhb@FreeBSD.org>
Subject: Re: panic: blockable sleep lock (sleep mutex) process 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: Tue, 15 Apr 2003 10:50:39 -0000

On Mon, Apr 14, 2003 at 11:33:18PM +0100, Paul Richards wrote:
> On Mon, Apr 14, 2003 at 10:10:21PM +0200, Pawel Worach wrote:
> > Yes they are, it's been like this for about a week or so
> > the latest working kernel i have is:
> > FreeBSD darkstar 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Apr  8 02:59:24
> > CEST 2003     root@darkstar:/usr/obj/usr/src/sys/DARKSTAR  i386
> > 
> 
> I have the same problem, and the same last working date.
> 
> I'm building a kernel from the 9th at the moment to try and pinpoint
> exactly when this broke.

I have a working kernel from the 11th and a broken kernel from the 12th.
I'll do some more tracking down this evening but something definitely
broke in that 24 hours.

I think someone else reported that SCHED_4BSD is still working ok, in
which case it must be one of the commits to sched_ule.c on that day, and
there look to be some patches that might cause this but I've not managed
to identify which one yet, or even confirmed that SCHED_4BSD is actually
working (needed sleep).

More tonight unless someone fixes it in the meantime :-)

Paul.