Date: Tue, 8 Apr 1997 16:02:53 +0100 (BST) From: Ian Pallfreeman <ip@mcc.ac.uk> To: freebsd-questions@freebsd.org Subject: wdx interrupt timeouts Message-ID: <199704081502.QAA11310@albatross.mcc.ac.uk>
next in thread | raw e-mail | index | archive | help
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. Commonality, FWIW, is that both machines are fast (for PCs), both are IDE+SCSI machines, and both have two identical IDE disks ccd striped on wd2/3. $Id: wd.c,v 1.128 1997/04/03 09:43:50 phk Exp $Id: ccd.c,v 1.22 1997/03/24 11:23:21 bde Exp wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): <QUANTUM LP52A 950509105>, 32-bit, multi-block-64 wd0: 49MB (102136 sectors), 751 cyls, 8 heads, 17 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa wdc1: unit 0 (wd2): <QUANTUM FIREBALL_TM3840A>, 32-bit, multi-block-16 wd2: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (wd3): <QUANTUM FIREBALL_TM3840A>, 32-bit, multi-block-16 wd3: 3681MB (7539840 sectors), 7480 cyls, 16 heads, 63 S/T, 512 B/S Suggestions, please, anyone? Ian.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704081502.QAA11310>