From: Jens Axboe <axboe@kernel.dk>
To: Meelis Roos <mroos@linux.ee>, Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: blk-mq problem on proliant DL380 G3 (cciss)
Date: Wed, 29 Oct 2014 14:13:46 -0600 [thread overview]
Message-ID: <54514A7A.8050008@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.11.1410292205060.16678@adalberg.ut.ee>
On 10/29/2014 02:06 PM, Meelis Roos wrote:
>> On Wed, Oct 29, 2014 at 09:08:46AM -0600, Jens Axboe wrote:
>>>> Another test server with MPT SCSI RAID has similar problem,
>>>> scsi_mode.use_blk_mq=0 cures it but I can not get good trace (no serail
>>>> console). 3.18.0-rc2-00043-gf7e87a4 was tested there.
>>>
>>> The first issue looks like scsi cdrom and error handling, it must be leaking
>>> requests hence we hang on allocation of a new one. cciss doesn't use blk_mq
>>> regardless of the scsi setting. Does the mpt box also have a libata driven
>>> cdrom?
>>
>> cciss does use scsi for CDROMs and other external devices, it is a bit
>> of a mess.
>>
>> Meelis, did you also test scsi-mq on 3.17 and this is a regression, or
>> was 3.18-rc2 the first kernel you tested?
>
> Both machines ran 3.17 successfully. I turned on scsi-mq option as soon
> as it appeared in Kconfig as a new option. But I am not sure whan the
> option appeared, before or after 3.17 release.
So just to be fully clear, you never enabled scsi-mq on 3.17? To do
that, you would have had to add a scsi_mod.use_blk_mq=1 boot parameter.
The scsi-mq kconfig option did not show up until after 3.17 release.
--
Jens Axboe
next prev parent reply other threads:[~2014-10-29 20:13 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 [this message]
2014-10-30 5:46 ` Meelis Roos
2014-10-30 11:18 ` Meelis Roos
2014-10-30 15:19 ` Christoph Hellwig
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=54514A7A.8050008@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox