[ Monday, January 31, 2000 ] Rainer Mager wrote:
> Feb 1 02:48:01 dual kernel: scsi : aborting command due to timeout : pid
> 10920, scsi1, channel 0, id 0, lun 0 Read (6) 00 06 df 60 00
> Feb 1 02:48:03 dual kernel: scsi : aborting command due to timeout : pid
> 10921, scsi1, channel 0, id 1, lun 0 Read (6) 00 07 c7 08 00
> Feb 1 02:48:03 dual kernel: scsi : aborting command due to timeout : pid
> 10922, scsi1, channel 0, id 1, lun 0 Read (6) 00 07 d7 48 00
> Feb 1 02:48:31 dual kernel: scsi : aborting command due to timeout : pid
> 10919, scsi1, channel 0, id 0, lun 0 Read (6) 00 06 bf 18 00
> Feb 1 02:48:31 dual kernel: scsi : aborting command due to timeout : pid
> 10920, scsi1, channel 0, id 0, lun 0 Read (6) 00 06 df 60 00
Tell us how the 4 (5?) drives are scattered among the 2 controllers (2
channels of one controller?), which id's, etc. The above looks like my
3960D problem that went away when I added "noapic" on my BP6 board.
Perhaps it's a termination issue since it looks limited to 2 drives on
one controller? Just a guess.
In any case, I wouldn't bother with the md layer until you can get all
the scsi drives acting happy for extended periods of time :)
James
--
Miscellaneous Engineer --- IBM Netfinity Performance Development
