From owner-freebsd-current@FreeBSD.ORG Thu Apr 17 10:13:16 2003 Return-Path: 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 69F2037B401 for ; Thu, 17 Apr 2003 10:13:16 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A780143FBD for ; Thu, 17 Apr 2003 10:13:13 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) h3HHD2PR029713; Thu, 17 Apr 2003 10:13:02 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)h3HHD1W1029712; Thu, 17 Apr 2003 10:13:01 -0700 (PDT) Date: Thu, 17 Apr 2003 10:13:01 -0700 From: Steve Kargl To: Paul Richards Message-ID: <20030417171301.GA29549@troutmask.apl.washington.edu> References: <20030414192627.C32D543F3F@mx1.FreeBSD.org> <20030414170306.C70262@alpha.siliconlandmark.com> <20030414211310.I5215@hub.org> <20030417163642.GI23466@survey.codeburst.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030417163642.GI23466@survey.codeburst.net> User-Agent: Mutt/1.4i cc: pawel.worach@telia.com cc: Andre Guibert de Bruet cc: current@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2003 17:13:16 -0000 On Thu, Apr 17, 2003 at 05:36:43PM +0100, Paul Richards wrote: > On Mon, Apr 14, 2003 at 09:13:54PM +0000, The Hermit Hacker wrote: > > On Mon, 14 Apr 2003, Andre Guibert de Bruet wrote: > > > > > Pawel, > > > > > > Last I've heard, SCHED_ULE isn't SMP friendly. > > I haven't been able to build a SCHED_ULE working kernel since 11 April. > It has dies with the blockable sleep lock as per this thread and I've > been trying a new kernel each day but it's still broken. > > I tried to track down the commit and I know it exists in a kernel built > later than 12th but I haven't pinpointed the exact commit yet. > Are your running a UP or SMP system? My laptop and home system are both running a 14 April ULE kernel/world without any problems. Both systems are UP. -- Steve