From owner-freebsd-current@FreeBSD.ORG Mon Jul 12 20:36:05 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 03F9216A4CE; Mon, 12 Jul 2004 20:36:05 +0000 (GMT) Received: from av4-2-sn3.vrr.skanova.net (av4-2-sn3.vrr.skanova.net [81.228.9.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C04243D3F; Mon, 12 Jul 2004 20:36:04 +0000 (GMT) (envelope-from manlix@demonized.net) Received: by av4-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 972F837E9D; Mon, 12 Jul 2004 22:36:03 +0200 (CEST) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av4-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 8420237E46; Mon, 12 Jul 2004 22:36:03 +0200 (CEST) Received: from fisk.demonized.net (h144n2fls33o834.telia.com [213.66.186.144]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id A1DFF37E48; Mon, 12 Jul 2004 22:35:59 +0200 (CEST) Received: from beard.demonized.net (beard.demonized.net [192.168.0.2]) by fisk.demonized.net (Postfix) with SMTP id 3588C60EC; Mon, 12 Jul 2004 22:36:07 +0200 (CEST) Date: Mon, 12 Jul 2004 22:35:57 +0200 From: Johan Pettersson To: Robert Watson Message-Id: <20040712223557.095e8b1c.manlix@demonized.net> In-Reply-To: References: 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:36:05 -0000 > 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. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee > Research > Do you or John or any one else know whats can cause this? Is there any ongoing work to fix this?