From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Tomi Sarvela <tomi.p.sarvela@intel.com>,
linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: linux-next scsi-mq hang in suspend-resume
Date: Fri, 14 Jul 2017 05:44:24 -0700 [thread overview]
Message-ID: <20170714124424.GA28150@infradead.org> (raw)
In-Reply-To: <20170713071220.GA19972@infradead.org>
Tomi,
can you please report what hardware this is one (e.g. libata or
real scsi, which driver), a kernel config and the actual command
used to suspend the system (to ram, to disk?) so that I an try to
reproduce it?
next prev parent reply other threads:[~2017-07-14 12:44 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 [this message]
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
-- 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=20170714124424.GA28150@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).