From: Christoph Hellwig <hch@infradead.org>
To: Meelis Roos <mroos@linux.ee>
Cc: Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
linux-scsi@vger.kernel.org
Subject: Re: blk-mq problem on proliant DL380 G3 (cciss)
Date: Thu, 30 Oct 2014 08:19:55 -0700 [thread overview]
Message-ID: <20141030151955.GA12158@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.11.1410301317340.19899@adalberg.ut.ee>
Meelis,
can you try the patch below? It's a hack and not a proper fix, but it
addresses what seems to be your culprit, given that it is the only
place allocating a request from the error handler.
diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
index fa7b5ec..5804ea0 100644
--- a/drivers/scsi/scsi_error.c
+++ b/drivers/scsi/scsi_error.c
@@ -2010,6 +2010,7 @@ static void scsi_restart_operations(struct Scsi_Host *shost)
struct scsi_device *sdev;
unsigned long flags;
+#if 0
/*
* If the door was locked, we need to insert a door lock request
* onto the head of the SCSI request queue for the device. There
@@ -2019,6 +2020,7 @@ static void scsi_restart_operations(struct Scsi_Host *shost)
if (scsi_device_online(sdev) && sdev->locked)
scsi_eh_lock_door(sdev);
}
+#endif
/*
* next free up anything directly waiting upon the host. this
next prev parent reply other threads:[~2014-10-30 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 10:47 blk-mq problem on proliant DL380 G3 (cciss) Meelis Roos
2014-10-29 11:46 ` Meelis Roos
2014-10-29 15:08 ` Jens Axboe
2014-10-29 15:38 ` Meelis Roos
2014-10-29 22:50 ` Elliott, Robert (Server Storage)
2014-10-29 18:38 ` Christoph Hellwig
2014-10-29 20:06 ` Meelis Roos
2014-10-29 20:13 ` Jens Axboe
2014-10-30 5:46 ` Meelis Roos
2014-10-30 11:18 ` Meelis Roos
2014-10-30 15:19 ` Christoph Hellwig [this message]
2014-10-30 17:32 ` Meelis Roos
2014-10-30 17:45 ` Christoph Hellwig
2014-11-03 1:23 ` Jens Axboe
2014-11-03 10:08 ` Christoph Hellwig
2014-11-03 13:05 ` Meelis Roos
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=20141030151955.GA12158@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-scsi@vger.kernel.org \
--cc=mroos@linux.ee \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.