Date: Sun, 29 Oct 2000 10:22:22 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Motomichi Matsuzaki <mzaki@e-mail.ne.jp> Cc: wpaul@freebsd.org, freebsd-current@freebsd.org Subject: Re: dc0: watchdog timeout Message-ID: <14844.16183.229740.388514@grasshopper.cs.duke.edu> In-Reply-To: <86hf62eovy.wl@tkc.att.ne.jp> References: <14836.62663.657129.698427@grasshopper.cs.duke.edu> <86hf62eovy.wl@tkc.att.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14844.16183.229740.388514>