Date: Fri, 10 Nov 2000 19:06:20 +0100 From: Andre Oppermann <oppermann@telehouse.ch> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: John Baldwin <jhb@FreeBSD.ORG>, alpha@FreeBSD.ORG Subject: Re: Does your Alpha run a SMPng kernel? Message-ID: <3A0C391C.63273AA7@telehouse.ch> References: <14859.23664.641868.642173@grasshopper.cs.duke.edu> <XFMail.001109185513.jhb@FreeBSD.org> <14860.13678.594397.310814@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Gallatin wrote: > > John Baldwin writes: > > > > Have any clues as to where it is hanging? One thing that may help is that I > > This is the "one device goes south but everything else is happy" sort > of problem I was complaining about last week. > > My UP1000 running today's -current just wedged while I was rcp'ing a > large file to it over a 100Mb link. It's busy speweing "fxp0: device > timeout" Everything but the nic seems happy. (But since I'm running > with NIS and NFS, loosing the nic is fatal) -snip- > fxp0: device timeout > fxp0: device timeout > fxp0: device timeout > > Is there a chance that this is being caused by the kernel, say, > getting a clock interrupt in the middle of doing some low-level > should-be-atomic timing-dependant I/O operations in either the driver > or the I/O support routines? > > Remember that on the UP1000, everything goes through the isa interrupt > controller. I get this error as well but I'm on i386. AMD Athlon 900 to be exact. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A0C391C.63273AA7>