On 12-Jun-2001 Stephen Simmons wrote:
> [snip]
> scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0
> Read (10) 00 00 00 00 10 00 00 01 00
> scsi0 channel 0 : resetting for second half of retries.
> SCSI bus is being reset for host 0 channel 0.
> I/O error: dev 0b:00, sector 64
> isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=32
> scsi0 : channel 0 target 0 lun 0 request sense failed, performing reset.
> SCSI bus is being reset for host 0 channel 0.
>
> The last message repeated a number of times. As you can see, it ATAPI
> interface seems to have figured out that there was a problem, but the
> SCSI seems to have hung (?).
>
> Finally, I got a "kernel panic" with "Aiee in interrupt handler" and
> "not syncing"
> [snip]
The tendency of the linux scsi subsystem to crash with "Aiee in interrupt
handler" after several scsi-recovery-attempts with "resetting for second half of
retries" seems to be unrelated to ide-scsi.
I reproduced it many times in the past with aic7xxx, sd and handselected, bad
MO-drives, which are slow enough to produce timeouts in "normal" operation. (sd
badly lacks configurable timeouts).
I saw this behaviour at least in kernels 2.3.(about 50) up to 2.4.2 and
independent of the scsi hostbus-adaptor.
Regards,
Ralf
-----------------------------------------------------------------
| Ralf Oehler
| GDI - Gesellschaft fuer Digitale Informationstechnik mbH
|
| E-Mail: [EMAIL PROTECTED]
| Tel.: +49 6182-9271-23
| Fax.: +49 6182-25035
| Mail: GDI, Bensbruchstra�e 11, D-63533 Mainhausen
| HTTP: www.GDImbH.com
-----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
