From: Christoph Hellwig <hch@infradead.org>
To: Tomi Sarvela <tomi.p.sarvela@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: linux-next scsi-mq hang in suspend-resume
Date: Mon, 17 Jul 2017 03:35:19 -0700 [thread overview]
Message-ID: <20170717103519.GA13473@infradead.org> (raw)
In-Reply-To: <6831a724-3b4b-be48-c561-8fd1e8c7ebe0@intel.com>
On Mon, Jul 17, 2017 at 01:30:00PM +0300, Tomi Sarvela wrote:
> First, tested that next-20170717 still triggers the problem when no extra
> options given. Adding scsi_mod.use_blk_mq=0 makes tests work.
>
> Then I tried with sd.diff patched next-20170717. Works (still) with
> use_blk_mq=0. Also works when no options given, so this patch avoids the
> hang when using the new block-mq.
>
> These tests on generic Haswell 4790K desktop machine.
Thanks Tomi,
this seems to confirm it's runtime PM related, although I don't
really understand why that's an issue. Let me spin up an implementation
of RQF_PM for blk-mq and give it to you for testing.
next prev parent reply other threads:[~2017-07-17 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 14:51 linux-next scsi-mq hang in suspend-resume Tomi Sarvela
2017-07-12 16:50 ` Jens Axboe
2017-07-13 7:12 ` Christoph Hellwig
2017-07-14 12:44 ` Christoph Hellwig
2017-07-14 13:33 ` Tomi Sarvela
2017-07-17 7:53 ` Christoph Hellwig
2017-07-17 10:30 ` Tomi Sarvela
2017-07-17 10:35 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-17 15:18 Evangelos Foutras
2017-07-17 17:17 ` Evangelos Foutras
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=20170717103519.GA13473@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=tomi.p.sarvela@intel.com \
/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).