From owner-freebsd-current@FreeBSD.ORG  Mon Apr 14 15:35:33 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 105F237B401
	for <current@FreeBSD.org>; Mon, 14 Apr 2003 15:35:33 -0700 (PDT)
Received: from h14n2fls34o809.telia.com (h190n1fls34o809.telia.com
	[213.67.96.190])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C1B8543F3F
	for <current@FreeBSD.org>; Mon, 14 Apr 2003 15:35:31 -0700 (PDT)
	(envelope-from pawel.worach@telia.com)
Received: from corona (corona.sajd.net [192.168.1.20])h3EMZTg00571
	for <current@FreeBSD.org>; Tue, 15 Apr 2003 00:35:30 +0200 (MEST)
From: "Pawel Worach" <pawel.worach@telia.com>
To: <current@FreeBSD.org>
Date: Tue, 15 Apr 2003 00:35:29 +0200
Message-ID: <000001c302d6$275366e0$1401a8c0@corona>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <XFMail.20030414155909.jhb@FreeBSD.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
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: Mon, 14 Apr 2003 22:35:33 -0000

Well I have been using ULE since it was committed without any
problems up until now.

I re-cvsupped src/sys just to make sure my sources are clean but
it still panics. I also build a 4BSD sched kernel that boots fine.

On Mon, 14 Apr 2003, Andre Guibert de Bruet wrote:

> Pawel,
>
> Last I've heard, SCHED_ULE isn't SMP friendly.

I'm running SCHED_ULE on a DualAMD desktop at the office, and haven't
noticed any instability issues ...