From owner-freebsd-current Sun Oct 29 11:30:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from webcom.it (unknown [213.205.4.2]) by hub.freebsd.org (Postfix) with SMTP id A146437B4C5 for ; Sun, 29 Oct 2000 11:30:43 -0800 (PST) Received: (qmail 10944 invoked by uid 1000); 30 Oct 2000 17:24:38 -0000 Message-ID: <20001030172438.10943.qmail@webcom.it> From: andrea@webcom.it Subject: * watchdog timeout (Was: dc0: watchdog timeout) In-Reply-To: <14844.16183.229740.388514@grasshopper.cs.duke.edu> "from Andrew Gallatin at Oct 29, 2000 10:22:22 am" To: freebsd-current@freebsd.org Date: Mon, 30 Oct 2000 18:24:38 +0100 (CET) Cc: Motomichi Matsuzaki , wpaul@freebsd.org X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably not related at all, but on -current I am seeing: xe0: watchdog timeout; resetting card It happens just once, at boot time or after I insert the PC Card (Compaq whatever). After that, everything works ok. Andrew Gallatin wrote: > > 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 > -- The computer revolution is over. The computers won. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message