Date: Mon, 12 Jul 2004 22:56:12 +0200 From: Johan Pettersson <manlix@demonized.net> To: Robert Watson <rwatson@freebsd.org> Cc: skywizard@mybsd.org.my Subject: Re: Native preemption is the culprit [was Re: today's CURRENT lockups] Message-ID: <20040712225612.3ba37729.manlix@demonized.net> In-Reply-To: <Pine.NEB.3.96L.1040712163724.52015B-100000@fledge.watson.org> References: <20040712223557.095e8b1c.manlix@demonized.net> <Pine.NEB.3.96L.1040712163724.52015B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> It's not currently clear what the cause is -- reports suggest that > it's an existing bug that's getting triggered by preemption, although > I wouldn't rule out a bug in the preemption implementation itself. > I'm currently setting up a box with NMI to see if I can get some more > useful information, as serial break isn't cutting it (suggesting a > leaked spin lock or critical section). I don't have an ETA, but I'm > guessing that we'll have some sort of resolution in the next day or > two. If not, I guess we back out the change, or disable PREEMPTION by > default. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee > Research > Okey... Im going to build a kernel with #define PREEMPTION disabled now. Its too annoying to get lock-ups all the time. :) Shout when you have some code to be tested.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040712225612.3ba37729.manlix>