From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 20:56:16 2004 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 7709816A4CE; Mon, 12 Jul 2004 20:56:16 +0000 (GMT) Received: from av6-1-sn3.vrr.skanova.net (av6-1-sn3.vrr.skanova.net [81.228.9.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B26443D3F; Mon, 12 Jul 2004 20:56:16 +0000 (GMT) (envelope-from manlix@demonized.net) Received: by av6-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 40BB737F53; Mon, 12 Jul 2004 22:56:15 +0200 (CEST) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av6-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 31BE237EBD; Mon, 12 Jul 2004 22:56:15 +0200 (CEST) Received: from fisk.demonized.net (h144n2fls33o834.telia.com [213.66.186.144]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 6CE3F37E4C; Mon, 12 Jul 2004 22:56:14 +0200 (CEST) Received: from beard.demonized.net (beard.demonized.net [192.168.0.2]) by fisk.demonized.net (Postfix) with SMTP id A786C60EC; Mon, 12 Jul 2004 22:56:22 +0200 (CEST) Date: Mon, 12 Jul 2004 22:56:12 +0200 From: Johan Pettersson To: Robert Watson Message-Id: <20040712225612.3ba37729.manlix@demonized.net> In-Reply-To: References: <20040712223557.095e8b1c.manlix@demonized.net> X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd5.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: avleeuwen@piwebs.com cc: skywizard@mybsd.org.my Subject: Re: Native preemption is the culprit [was Re: today's CURRENT lockups] 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: Mon, 12 Jul 2004 20:56:16 -0000 > 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.