From owner-freebsd-alpha  Thu Nov 16  7: 9:33 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3481A37B479; Thu, 16 Nov 2000 07:09:31 -0800 (PST)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA09673;
	Thu, 16 Nov 2000 10:09:30 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAGF9UQ39575;
	Thu, 16 Nov 2000 10:09:30 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 16 Nov 2000 10:09:30 -0500 (EST)
To: freebsd-alpha@freebsd.org
Cc: jhb@freebsd.org
Subject: SMPng stability
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14867.63252.979175.633781@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


John Baldwin's most recent commits (the ones leading up to WITNESS
working) seem to have improved the stability SMPng on alpha.  I'd urge
anybody who is having -current stability problems on alpha to update
your sources and try a new kernel.

It is admittedly a bit early to tell, but I cannot make my UP1000
loose its network adapter anymore.  Yesterday I could induce 'fxp0:
device timeout' by running gdb on a kernel.debug mounted via NFS.  I'm
going to see if my home miata will survive a buildworld/installworld
tonight; it was always the real problem child...

Heck, this might even help the PC164 situation..

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message