Date: Wed, 9 Apr 1997 21:24:49 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Ian Pallfreeman <ip@mcc.ac.uk> Cc: freebsd-questions@freebsd.org Subject: Re: wdx interrupt timeouts Message-ID: <Pine.BSF.3.96.970409212407.4997k-100000@localhost> In-Reply-To: <199704081502.QAA11310@albatross.mcc.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 8 Apr 1997, Ian Pallfreeman wrote: > I've been seeing messages similar to: > > Apr 8 15:07:54 lurch /kernel: wd3: interrupt timeout: > Apr 8 15:07:54 lurch /kernel: wd3: status 58<rdy,seekdone,drq> error 0 > Apr 8 15:46:05 lurch /kernel: wd3: interrupt timeout: > Apr 8 15:46:05 lurch /kernel: wd3: status 50<rdy,seekdone> error 1<no_dam> > > for some time on my home P200 with second-hand IBM disks, and assumed that it > was simply the disks being slightly naughty. However, this machine (lurch) is > a P-Pro 200 with two brand-new 3.8Gb Quantum Fireballs. Do you have IDE spindown enabled? That's what it looks like happened-- wd3 spun down and the system tried to poke it, and it took a little too long to come back to ready. Nothing to worry about. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970409212407.4997k-100000>