* scsi error handler thread seems to run continuously
@ 2010-05-28 21:07 Jeff Moyer
2010-05-28 21:55 ` Mike Snitzer
0 siblings, 1 reply; 3+ messages in thread
From: Jeff Moyer @ 2010-05-28 21:07 UTC (permalink / raw)
To: linux-scsi
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.
Thanks,
Jeff
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: scsi error handler thread seems to run continuously
2010-05-28 21:07 scsi error handler thread seems to run continuously Jeff Moyer
@ 2010-05-28 21:55 ` Mike Snitzer
2010-05-28 23:30 ` Jeff Moyer
0 siblings, 1 reply; 3+ messages in thread
From: Mike Snitzer @ 2010-05-28 21:55 UTC (permalink / raw)
To: Jeff Moyer; +Cc: linux-scsi, David Zeuthen
On Fri, May 28, 2010 at 5:07 PM, Jeff Moyer <jmoyer@redhat.com> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: scsi error handler thread seems to run continuously
2010-05-28 21:55 ` Mike Snitzer
@ 2010-05-28 23:30 ` Jeff Moyer
0 siblings, 0 replies; 3+ messages in thread
From: Jeff Moyer @ 2010-05-28 23:30 UTC (permalink / raw)
To: Mike Snitzer; +Cc: linux-scsi, David Zeuthen
Mike Snitzer <snitzer@redhat.com> writes:
> 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.
Ahh, silence. On my system, hald-addon-storage was polling /dev/sr0
every 2 seconds. Killing this process, there's now nothing going on.
Thanks a ton!
-Jeff
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-05-28 23:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-28 21:07 scsi error handler thread seems to run continuously Jeff Moyer
2010-05-28 21:55 ` Mike Snitzer
2010-05-28 23:30 ` Jeff Moyer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).