From owner-freebsd-current  Sun Oct 29  7:22:25 2000
Delivered-To: freebsd-current@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id B792637B479; Sun, 29 Oct 2000 07:22:23 -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 KAA21972;
	Sun, 29 Oct 2000 10:22:22 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e9TFMMR75313;
	Sun, 29 Oct 2000 10:22:22 -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: Sun, 29 Oct 2000 10:22:22 -0500 (EST)
To: Motomichi Matsuzaki <mzaki@e-mail.ne.jp>
Cc: wpaul@freebsd.org, freebsd-current@freebsd.org
Subject: Re: dc0: watchdog timeout
In-Reply-To: <86hf62eovy.wl@tkc.att.ne.jp>
References: <14836.62663.657129.698427@grasshopper.cs.duke.edu>
	<86hf62eovy.wl@tkc.att.ne.jp>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14844.16183.229740.388514@grasshopper.cs.duke.edu>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


To follow up on this, after switching from a dc0 to an fxp0 I finally
managed to wedge my -current UP1000 with heavy CPU & NFS activity
(starting up the linux mozilla).  It is now speweing 'fxp0: device
timeout' to the console (and inconveniently ignoring breaks on the
serial console).

So it appears that it is not dc specific (though it 
does seem to happen much more fequently 21143's)

I guess its either alpha or SMPng specific..

Drew


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