Date: Tue, 15 Apr 2003 11:50:32 +0100 From: Paul Richards <paul@freebsd-services.com> To: Pawel Worach <pawel.worach@telia.com> Cc: 'John Baldwin' <jhb@FreeBSD.org> Subject: Re: panic: blockable sleep lock (sleep mutex) process lock Message-ID: <20030415105032.GB93652@survey.codeburst.net> In-Reply-To: <20030414223318.GA75035@survey.codeburst.net> References: <XFMail.20030414155909.jhb@FreeBSD.org> <000201c302c1$e0d1dee0$1401a8c0@corona> <20030414223318.GA75035@survey.codeburst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030415105032.GB93652>