Maybe mine sees more disk activity than most, but pre8 and pre9 die
with SCSI errors whenever they hit a really big load of disk activity
(like doing a find over the whole disk, which happens every morning at
6:30 or so...).
I can't help but notice that the version of the NCR driver appears to
have changed with pre8. This didn't happen with older versions.
I get the following messages:
Jan 25 06:39:27 mdorman kernel: scsi : aborting command due to timeout : pid 33130, scsi0, channel 0, id 0, lun 0 0x2a 00 00 2c 00 f0 00 00 02 00
Jan 25 06:39:27 mdorman kernel: ncr53c8xx_abort: pid=33130 serial_number=33137 serial_number_at_timeout=33137
Jan 25 06:39:27 mdorman kernel: ncr53c810-0: abort ccb=fffffc0000008820 (cancel)
Jan 25 06:39:29 mdorman kernel: SCSI host 0 abort (pid 33130) timed out - resetting
Jan 25 06:39:30 mdorman kernel: SCSI bus is being reset for host 0 channel 0.
Jan 25 06:39:30 mdorman kernel: ncr53c8xx_reset: pid=33130 reset_flags=2 serial_number=33137 serial_number_at_timeout=33137
Jan 25 06:39:30 mdorman kernel: ncr53c810-0: restart (scsi reset).
Jan 25 06:39:31 mdorman kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2603007f
Jan 25 06:39:31 mdorman kernel: scsidisk I/O error: dev 08:02, sector 2850840
Jan 25 06:39:34 mdorman kernel: scsi0 channel 0 : resetting for second half of retries.
Jan 25 06:39:34 mdorman kernel: SCSI bus is being reset for host 0 channel 0.
Jan 25 06:39:34 mdorman kernel: ncr53c8xx_reset: pid=33131 reset_flags=1 serial_number=0 serial_number_at_timeout=0
Jan 25 06:39:34 mdorman kernel: scsi0: device driver called scsi_done() for a syncronous reset.
Jan 25 06:39:34 mdorman kernel: ncr53c810-0: restart (scsi reset).
Jan 25 06:39:35 mdorman kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2603007f
Jan 25 06:39:35 mdorman kernel: scsidisk I/O error: dev 08:02, sector 2850860
Jan 25 06:40:00 mdorman kernel: scsi0 channel 0 : resetting for second half of retries.
Jan 25 06:40:00 mdorman kernel: SCSI bus is being reset for host 0 channel 0.
Jan 25 06:40:00 mdorman kernel: ncr53c8xx_reset: pid=33132 reset_flags=1 serial_number=0 serial_number_at_timeout=0
Jan 25 06:40:00 mdorman kernel: scsi0: device driver called scsi_done() for a syncronous reset.
Jan 25 06:40:00 mdorman kernel: ncr53c810-0: restart (scsi reset).
Jan 25 06:40:01 mdorman kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2603007f
Jan 25 06:40:01 mdorman kernel: scsidisk I/O error: dev 08:02, sector 2850840
Jan 25 06:40:01 mdorman kernel: EXT2-fs error (device 08:02): ext2_write_inode: unable to read inode block - inode=356358, block=1425420
Jan 25 06:40:04 mdorman kernel: scsi0 channel 0 : resetting for second half of retries.
Jan 25 06:40:04 mdorman kernel: SCSI bus is being reset for host 0 channel 0.
Jan 25 06:40:04 mdorman kernel: ncr53c8xx_reset: pid=33133 reset_flags=1 serial_number=0 serial_number_at_timeout=0
Jan 25 06:40:04 mdorman kernel: scsi0: device driver called scsi_done() for a syncronous reset.
Jan 25 06:40:04 mdorman kernel: ncr53c810-0: restart (scsi reset).
Jan 25 06:40:06 mdorman kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2603007f
Jan 25 06:40:06 mdorman kernel: scsidisk I/O error: dev 08:02, sector 3228898
Jan 25 06:40:07 mdorman kernel: SCSI disk error : host 0 channel 0 id 0 lun 0 return code = 2603007f
Jan 25 06:40:07 mdorman kernel: scsidisk I/O error: dev 08:02, sector 2850860
Jan 25 06:40:07 mdorman kernel: EXT2-fs error (device 08:02): ext2_write_inode: unable to read inode block - inode=356440, block=1425430
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/