From: Jens Axboe <axboe@kernel.dk>
To: Mike Galbraith <efault@gmx.de>, Paolo Valente <paolo.valente@linaro.org>
Cc: Christoph Hellwig <hch@lst.de>,
linux-block <linux-block@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Oleksandr Natalenko <oleksandr@natalenko.name>
Subject: Re: bug in tag handling in blk-mq?
Date: Tue, 8 May 2018 14:37:52 -0600 [thread overview]
Message-ID: <3692ce7d-a767-72e6-65ae-6178b6c2e7d8@kernel.dk> (raw)
In-Reply-To: <1525797766.5204.2.camel@gmx.de>
On 5/8/18 10:42 AM, Mike Galbraith wrote:
> On Tue, 2018-05-08 at 08:55 -0600, Jens Axboe wrote:
>>
>> All the block debug files are empty...
>
> Sigh. Take 2, this time cat debug files, having turned block tracing
> off before doing anything else (so trace bits in dmesg.txt should end
> AT the stall).
OK, that's better. What I see from the traces:
- You have regular IO and some non-fs IO (from scsi_execute()). This mix
may be key.
- sdd has nothing pending, yet has 6 active waitqueues.
I'm going to see if I can reproduce this. Paolo, what kind of attempts
to reproduce this have you done?
--
Jens Axboe
next prev parent reply other threads:[~2018-05-08 20:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 14:03 Paolo Valente
2018-05-07 16:39 ` Jens Axboe
2018-05-07 18:02 ` Paolo Valente
2018-05-08 4:51 ` Mike Galbraith
2018-05-08 8:37 ` Mike Galbraith
2018-05-08 14:55 ` Jens Axboe
2018-05-08 16:42 ` Mike Galbraith
2018-05-08 20:37 ` Jens Axboe [this message]
2018-05-08 21:19 ` Jens Axboe
2018-05-09 1:09 ` Jens Axboe
2018-05-09 4:11 ` Mike Galbraith
2018-05-09 5:06 ` Paolo Valente
2018-05-09 15:18 ` Jens Axboe
2018-05-09 16:57 ` Mike Galbraith
2018-05-09 17:01 ` Jens Axboe
2018-05-09 18:31 ` Mike Galbraith
2018-05-09 19:50 ` Jens Axboe
2018-05-10 4:38 ` Mike Galbraith
2018-05-09 5:09 ` Mike Galbraith
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=3692ce7d-a767-72e6-65ae-6178b6c2e7d8@kernel.dk \
--to=axboe@kernel.dk \
--cc=efault@gmx.de \
--cc=hch@lst.de \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=ulf.hansson@linaro.org \
/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
Powered by JetHome