From: Jeff Moyer <jmoyer@redhat.com>
To: linux-scsi@vger.kernel.org
Subject: scsi error handler thread seems to run continuously
Date: Fri, 28 May 2010 17:07:57 -0400 [thread overview]
Message-ID: <x49wrunvioi.fsf@segfault.boston.devel.redhat.com> (raw)
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
next reply other threads:[~2010-05-28 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 21:07 Jeff Moyer [this message]
2010-05-28 21:55 ` scsi error handler thread seems to run continuously Mike Snitzer
2010-05-28 23:30 ` Jeff Moyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x49wrunvioi.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).