Re: [TCLUG:16363] irq timeout

[David Wood <jbevren@yahoo.com>]

Yeah.  I've been through bad harddisks quite a few times.   Each time the
drive starts to develop bad sectors, I see these timeouts (the drive takes
longer than expected to correct for errors on the physical surface).

I'd do a fsck -c (or whatever is required to check the surface for bad
blocks) right away, before any data is lost.

If it's a kernel issue (Which I doubt but pray is true), there's no problem
with your drive.

-David


On Tue, 18 Apr 2000, Chris Engstrom wrote:

> Date: Tue, 18 Apr 2000 12:04:59 -0500
> From: Chris Engstrom <bliss@bliss.treewax.com>
> Reply-To: tclug-list@mn-linux.org
> To: tclug-list@mn-linux.org
> Subject: [TCLUG:16363] irq timeout
> 
> this seems to be happening more and more
> Apr 17 18:54:37 bliss kernel: hdc: irq timeout: status=0xd0 { Busy }
> Apr 17 18:54:37 bliss kernel: hdc: ATAPI reset complete
> Apr 17 18:54:47 bliss kernel: hdc: irq timeout: status=0xd0 { Busy }
> Apr 17 18:54:47 bliss kernel: hdc: ATAPI reset complete
> Apr 17 18:54:57 bliss kernel: hdc: irq timeout: status=0xd0 { Busy }
> Apr 17 18:54:57 bliss kernel: hdc: ATAPI reset complete
> kernel 2.2.13 
> /dev/hdc is a cdrom
> 
> any ideas ? 
>