Date: Mon, 12 Jul 2004 16:39:24 -0400 (EDT) From: Robert Watson <rwatson@freebsd.org> To: Johan Pettersson <manlix@demonized.net> Cc: skywizard@mybsd.org.my Subject: Re: Native preemption is the culprit [was Re: today's CURRENT lockups] Message-ID: <Pine.NEB.3.96L.1040712163724.52015B-100000@fledge.watson.org> In-Reply-To: <20040712223557.095e8b1c.manlix@demonized.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Jul 2004, Johan Pettersson wrote: > > Per my earlier post, I've experienced similar unreliability. The work > > around I'm using is to build with "#define PREEMPTION" from param.h > > disabled. This results in a quite usable kernel, although quite > > probably more poor interrupt handling latency, etc. > > Do you or John or any one else know whats can cause this? Is there any > ongoing work to fix this? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1040712163724.52015B-100000>