From: Ingo Molnar <mingo@elte.hu>
To: linux-scsi@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Jens Axboe <jens.axboe@oracle.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: scsi: aic7xxx hang since v2.6.28-rc1 ...
Date: Sun, 15 Feb 2009 12:58:23 +0100 [thread overview]
Message-ID: <20090215115823.GB19464@elte.hu> (raw)
In-Reply-To: <20090215114446.GA19464@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> Here's an SCSI regression i tracked down recently. I'll follow up with
> more info.
I sent this to James Bottomley about a month ago, who suggested that the
bug looks similar to problems caused by:
| commit b60af5b0adf0da24c673598c8d3fb4d4189a15ce
| Author: Alan Stern <stern@rowland.harvard.edu>
| Date: Mon Nov 3 15:56:47 2008 -0500
|
| [SCSI] simplify scsi_io_completion()
I could not revert that patch because it had a lot of followup dependencies,
but by experimentation i figured out the following string of gradual reverts
to scsi_lib.c [the revert commits can be found in tip:out-of-tree]:
813104e: Revert "[SCSI] simplify scsi_io_completion()"
84db545: Revert "[SCSI] Fix uninitialized variable error in scsi_io_completion"
0eb6038: Revert "[SCSI] Fix error handling for DIF/DIX"
3cd94dd: Revert "[SCSI] scsi_lib: don't decrement busy counters when inserting commands"
c27aed5: Revert "[SCSI] scsi_lib: fix DID_RESET status problems"
These reverts solved the problem and the box has not locked up in the SCSI irq
completion code since then. The code has not had any changes upstream since i
did the reverts, so the bug is still relevant as of .29-rc5.
( James suggested i send this bugreport to this list too, so that it does not
get single-threaded on him as he is busy with other things - so more suggestions
are welcome. I can try proposed fix patches. James suggested the patch below
and i dont think it will show us much more than what we already know: that we
are looping in scsi_run_queue(). )
Ingo
diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
index 940dc32..5919dd0 100644
--- a/drivers/scsi/scsi_lib.c
+++ b/drivers/scsi/scsi_lib.c
@@ -593,6 +593,7 @@ static void scsi_run_queue(struct request_queue *q)
struct Scsi_Host *shost = sdev->host;
LIST_HEAD(starved_list);
unsigned long flags;
+ int count = 0;
if (scsi_target(sdev)->single_lun)
scsi_single_lun_run(sdev);
@@ -603,6 +604,8 @@ static void scsi_run_queue(struct request_queue *q)
while (!list_empty(&starved_list)) {
int flagset;
+ BUG_ON(count++ > 1000);
+
/*
* As long as shost is accepting commands and we have
* starved queues, call blk_run_queue. scsi_request_fn
next prev parent reply other threads:[~2009-02-15 11:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 11:44 Ingo Molnar
2009-02-15 11:58 ` Ingo Molnar [this message]
2009-02-17 20:10 ` Alan Stern
2009-02-18 15:58 ` Ingo Molnar
2009-02-18 19:16 ` Mike Anderson
2009-02-18 19:20 ` Ingo Molnar
2009-02-19 20:12 ` Alan Stern
2009-02-19 20:23 ` Ingo Molnar
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=20090215115823.GB19464@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®