From owner-freebsd-current@FreeBSD.ORG  Fri Jul  9 06:51:33 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 4DB1916A4CF
	for <freebsd-current@FreeBSD.org>;
	Fri,  9 Jul 2004 06:51:33 +0000 (GMT)
Received: from web14106.mail.yahoo.com (web14106.mail.yahoo.com
	[216.136.172.136])
	by mx1.FreeBSD.org (Postfix) with SMTP id 1E00443D49
	for <freebsd-current@FreeBSD.org>;
	Fri,  9 Jul 2004 06:51:33 +0000 (GMT)
	(envelope-from cguttesen@yahoo.dk)
Message-ID: <20040709065132.47775.qmail@web14106.mail.yahoo.com>
Received: from [194.248.174.58] by web14106.mail.yahoo.com via HTTP;
	Fri, 09 Jul 2004 08:51:32 CEST
Date: Fri, 9 Jul 2004 08:51:32 +0200 (CEST)
From: =?iso-8859-1?q?Claus=20Guttesen?= <cguttesen@yahoo.dk>
To: Taku YAMAMOTO <taku@tackymt.homeip.net>,
	John Baldwin <jhb@FreeBSD.org>
In-Reply-To: <20040709111955.2901ce5b.taku@tackymt.homeip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
cc: freebsd-current@FreeBSD.org
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jul 2004 06:51:33 -0000

> > This looks correct.  I'll test it locally first. 
> Has it worked for you all 
> > day?
> 
> My machine (HTT) has been up for 20 hours without a
> hang since last update.
> I tried to stress it in various ways (fsck -n,
> buildworld & buildkernel in
> parallel, burning a CD, etc.) but failed to crash
> it.
> 
> I'm bit afraid since the code is not tested on real
> SMP machines.
> How is it going on yours?

Applied the patch to current as of July 8'th on a dual
PIII @ 1 Ghz., ULE.

Did an db-import (4.7 GB) into postgresql,
nfs-exported /usr/src and did a buildworld from
another host, did a similar buildworld locally, no
lockups.

odin~#>uptime
 8:49am  up 16:22

No hickups so far.

regards
Claus


Yahoo! Mail (http://dk.mail.yahoo.com) - Gratis: 6 MB lagerplads, spamfilter og virusscan