On Wednesday 18 September 2002 07:03, Brian Jonnes wrote:
>Hi all,
>
>Still gnashing my teeth over this HP Colorado drive. Found some
> pointers which suggested disabling DMA -- have done so for both
> drives on that controller. Got 3 successful dumps since Thursday
> (>3GB written).
>
>The problem today is as follows. The dumps failed with an
> "Input/Output error" after 299kb written. When amcheck ran
> (without changing the tape) it failed before reading the tape. My
> logs give me:
>
>Sep 18 10:45:01 valhalla kernel: st: Version 20020205, bufsize
> 32768, wrt 30720, max init. bufs 4,
>s/g segs 16
>Sep 18 10:45:01 valhalla kernel: Attached scsi tape st0 at scsi0,
> channel 0, id 0, lun 0
>Sep 18 10:45:01 valhalla kernel: st0: Block limits 6684 - 1711130
> bytes. Sep 18 11:00:01 valhalla kernel: scsi : aborting command
> due to timeout : pid 329140, scsi0, channel 0, id 0, lun 0 Read
> (6) 01 00 00 40 00 Sep 18 11:00:01 valhalla kernel: hdd: irq
> timeout: status=0xc0 { Busy } Sep 18 11:00:02 valhalla kernel:
> hdd: ATAPI reset complete Sep 18 11:00:02 valhalla kernel: hdd:
> irq timeout: status=0x80 { Busy } Sep 18 11:00:02 valhalla
> kernel: hdd: ATAPI reset complete Sep 18 11:00:02 valhalla
> kernel: hdd: irq timeout: status=0x80 { Busy } Sep 18 11:00:02
> valhalla kernel: st0: Error 27070000 (sugg. bt 0x20, driver bt
> 0x7, host bt 0x7).
>Sep 18 11:20:01 valhalla kernel: st: Unloaded.
>
>Can I be sure that those IRQ timeouts are due to a faulty device?
> Can there be another explanation?
>
>Regards,
>
>Brian Jonnes

I've run into a similar situation, but on my cdrw. When the driver 
get its hole in the sock fixed, maybe, but till then its reboot 
time to re-initilalize and fix the driver.  One of the reasons to 
use scsi where scsi does it best I guess.

What kernel version again please?


-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.15% setiathome rank, not too shabby for a WV hillbilly