Date: Thu, 10 Apr 1997 11:22:35 +0100 (BST) From: Ian Pallfreeman <ip@mcc.ac.uk> To: freebsd-current@freebsd.org Subject: Re: wdx interrupt timeouts (fwd) Message-ID: <199704101022.LAA15505@albatross.mcc.ac.uk>
next in thread | raw e-mail | index | archive | help
I've switched this to the current list, since it's worse than I thought. Doug White wrote: > On Tue, 8 Apr 1997, Ian Pallfreeman wrote: > > 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 > > [...] > 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. Nothing to do with IDE spindown (had a couple of other folks suggesting that). This happens under heavy load -- e.g. mirroring the ftp archive. The problem has become worse over the last few days. First it changed to: Apr 9 14:06:48 lurch /kernel: wd3e: reverting to non-multi sector mode reading fsbn 4213504 of 4213456-4213518 (wd3 bn 4213504; cn 4180 tn 1 sn 1)wd3: status 59<rdy,seekdone,drq,err> error 40<uncorr> Apr 9 14:06:55 lurch /kernel: wd3e: hard error reading fsbn 4213506 of 4213456-4213518 (wd3 bn 4213506; cn 4180 tn 1 sn 3)wd3: status 59<rdy,seekdone,drq,err> error 40<uncorr> followed by a hang. Now it's giving a panic (integer divide overflow) whenever I try to read that block. Managed to get a dump, but kgdb won't tell me anything (can't find kstack). I guess I'll reformat the disks eventually; anybody got any other ideas? Ian.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704101022.LAA15505>