by I saw this in earlier kernels but wonder if anyone has a clue.
Dec 31 15:47:47 salsablanca kernel: SCSISEQ = 0x5a SEQADDR =
0x9 SSTAT0
= 0x10 SSTAT1 = 0x8a
Dec 31 15:47:47 salsablanca kernel: (scsi0:-1:-1:-1) Referenced SCB 0
not valid
during SELTO.
Dec 31 15:47:47 salsablanca kernel: SCSISEQ = 0x5a SEQADDR =
0x8 SSTAT0
= 0x10 SSTAT1 = 0x8a
Dec 31 15:47:47 salsablanca kernel: scsi : aborting command due to
timeout : pid
15169, scsi0, channel 0, id 0, lun 0 Write (10) 00 02 14 34 86 00 00
08 00
Dec 31 15:47:47 salsablanca kernel: scsi : aborting command due to
timeout : pid
15170, scsi0, channel 0, id 0, lun 0 Write (10) 00 00 00 00 4d 00 00
02 00
I am hoping it is not a hardware issue.
I see this also on a 2.2.17 kernel.
The 2.2.18 is monolithic and the 2.2.17 is modular for scsi.
This is a SEAGATE LVD 18gig drive.