Red Hat Bugzilla – Bug 83818
id-scsi errors SCSI bus is being reset ; scsi : aborting command due to timeout
Last modified: 2007-04-18 12:50:56 EDT
I get these errors with kernel-2.4.18-24.8.0 during cd-recording (or shortly after that) CDRW model: "LG CD-RW CED-8080B" I have kernel /vmlinuz-2.4.18-24.8.0 ro root=LABEL=/ hdc=ide-scsi in grub.conf. The burned CD seems OK. ------------ Error messages Feb 9 03:04:28 host133 kernel: SCSI host 0 abort (pid 1100854) timed out - resetting Feb 9 03:04:28 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 9 03:04:29 host133 kernel: scsi : aborting command due to timeout : pid 1100854, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 Feb 9 03:04:29 host133 kernel: SCSI host 0 abort (pid 1100854) timed out - resetting Feb 9 03:04:29 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 9 03:04:29 host133 kernel: scsi : aborting command due to timeout : pid 1100854, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 Feb 9 03:04:29 host133 kernel: SCSI host 0 abort (pid 1100854) timed out - resetting Feb 9 03:04:29 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 9 03:04:30 host133 kernel: scsi : aborting command due to timeout : pid 1100854, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 Feb 9 03:04:30 host133 kernel: SCSI host 0 abort (pid 1100854) timed out - resetting Feb 9 03:04:30 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 9 03:04:30 host133 kernel: scsi : aborting command due to timeout : pid 1100854, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 Feb 9 03:04:30 host133 kernel: SCSI host 0 abort (pid 1100854) timed out - resetting Feb 9 03:04:30 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 9 03:04:31 host133 kernel: scsi : aborting command due to timeout : pid 1100854, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 Feb 9 03:04:31 host133 kernel: SCSI host 0 abort (pid 1100854) timed out - resetting Feb 9 03:04:31 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 9 03:04:31 host133 kernel: scsi : aborting command due to timeout : pid 1100854, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 Feb 9 03:04:31 host133 kernel: SCSI host 0 abort (pid 1100854) timed out - resetting Feb 9 03:04:31 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 9 03:30:16 host133 kernel: attempt to access beyond end of device Feb 9 03:30:16 host133 kernel: 0b:00: rw=0, want=34, limit=2 Feb 9 03:30:16 host133 kernel: isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block=16 Feb 9 03:30:37 host133 kernel: attempt to access beyond end of device Feb 9 03:30:37 host133 kernel: 0b:00: rw=0, want=34, limit=2 Feb 9 03:30:37 host133 kernel: isofs_read_super: bread failed, dev=0b:00, iso_blknum=16, block:
These messages occure durig "Fixating" stage of cd-burning by cdrecord. Feb 10 01:55:05 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 10 01:55:05 host133 kernel: scsi : aborting command due to timeout : pid 1357655, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00 Feb 10 01:55:05 host133 kernel: SCSI host 0 abort (pid 1357655) timed out - resetting Feb 10 01:55:05 host133 kernel: SCSI bus is being reset for host 0 channel 0. Feb 10 01:55:06 host133 kernel: scsi : aborting command due to timeout : pid 1357655, scsi0, channel 0, id 0, lun 0 Test Unit Ready 00 00 00 00 00
Something else tried to access the bus but timed out (the fixate locks the bus for a long time). The kernel messages while scary are ok in this situation.