On Fri, May 28, 2010 at 5:07 PM, Jeff Moyer <jmoyer@xxxxxxxxxx> wrote: > Hi, > > If I turn up the scsi logging level to 0xff, I see the following in my > logs: > > May 28 17:04:12 solid kernel: scsi_block_when_processing_errors: rtn: 1 > May 28 17:04:12 solid kernel: Waking error handler thread > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 waking up > May 28 17:04:12 solid kernel: scsi_eh_1: flush finish cmd: ffff880115674580 > May 28 17:04:12 solid kernel: scsi_restart_operations: waking up host to restart > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 sleeping > May 28 17:04:12 solid kernel: Waking error handler thread > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 waking up > May 28 17:04:12 solid kernel: scsi_eh_1: flush finish cmd: ffff880115674580 > May 28 17:04:12 solid kernel: scsi_restart_operations: waking up host to restart > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 sleeping > May 28 17:04:12 solid kernel: Waking error handler thread > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 waking up > May 28 17:04:12 solid kernel: scsi_eh_1: flush finish cmd: ffff880115674580 > May 28 17:04:12 solid kernel: scsi_restart_operations: waking up host to restart > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 sleeping > May 28 17:04:12 solid kernel: Waking error handler thread > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 waking up > May 28 17:04:12 solid kernel: scsi_eh_1: flush finish cmd: ffff880115674580 > May 28 17:04:12 solid kernel: scsi_restart_operations: waking up host to restart > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 sleeping > May 28 17:04:12 solid kernel: Waking error handler thread > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 waking up > May 28 17:04:12 solid kernel: scsi_eh_1: flush finish cmd: ffff880115674580 > May 28 17:04:12 solid kernel: scsi_restart_operations: waking up host to restart > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 sleeping > May 28 17:04:12 solid kernel: Waking error handler thread > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 waking up > May 28 17:04:12 solid kernel: scsi_eh_1: flush finish cmd: ffff880115674580 > May 28 17:04:12 solid kernel: scsi_restart_operations: waking up host to restart > May 28 17:04:12 solid kernel: Error handler scsi_eh_1 sleeping > May 28 17:04:12 solid kernel: scsi_block_when_processing_errors: rtn: 1 > > Is this expected? Any ideas on what might be causing it? It's worth > noting that Mike Snitzer tried this on a scsi_debug device and saw the > same thing. Chatting with James on #storage we arrived at the fact that in my case the error handler was being triggered by: hald-addon-storage: polling /dev/sr0 (every 16 sec) Killing hald-addon-storage stops the 16s periodic scsi error handler messages. Turning debugging up (0xffffffff) shows: Error handler scsi_eh_1 sleeping sr 1:0:0:0: Done: 0xffff88007a8eb280 TIMEOUT sr 1:0:0:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK sr 1:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00 sr 1:0:0:0: scsi host busy 1 failed 0 Waking error handler thread Error handler scsi_eh_1 waking up scsi_eh_1: flush finish cmd: ffff88007a8eb280 sr 1:0:0:0: Notifying upper driver of completion (result 8000002) 0 sectors total, 0 bytes done. scsi_restart_operations: waking up host to restart sr 1:0:0:0: Send: 0xffff88007a8eb280 sr 1:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00 buffer = 0x(null), bufflen = 0, queuecommand 0xffffffff812a8d15 leaving scsi_dispatch_cmnd() Error handler scsi_eh_1 sleeping sr 1:0:0:0: Done: 0xffff88007a8eb280 TIMEOUT sr 1:0:0:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK sr 1:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00 sr 1:0:0:0: scsi host busy 1 failed 0 Waking error handler thread Error handler scsi_eh_1 waking up scsi_eh_1: flush finish cmd: ffff88007a8eb280 sr 1:0:0:0: Notifying upper driver of completion (result 8000002) 0 sectors total, 0 bytes done. scsi_restart_operations: waking up host to restart sr 1:0:0:0: Send: 0xffff88007a8eb280 sr 1:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00 buffer = 0x(null), bufflen = 0, queuecommand 0xffffffff812a8d15 leaving scsi_dispatch_cmnd() Error handler scsi_eh_1 sleeping -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
