From: Mike Galbraith <efault@gmx.de>
To: Jens Axboe <axboe@kernel.dk>, 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, 08 May 2018 18:42:46 +0200 [thread overview]
Message-ID: <1525797766.5204.2.camel@gmx.de> (raw)
In-Reply-To: <ffd0c030-43f8-0dbe-42b3-03bb9c410bea@kernel.dk>
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
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).
-Mike
[-- Attachment #2: dmesg.xz --]
[-- Type: application/x-xz, Size: 16992 bytes --]
[-- Attachment #3: dmesg.txt.xz --]
[-- Type: application/x-xz, Size: 21656 bytes --]
[-- Attachment #4: block_debug.xz --]
[-- Type: application/x-xz, Size: 1300 bytes --]
next prev parent reply other threads:[~2018-05-08 16:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 14:03 bug in tag handling in blk-mq? 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 [this message]
2018-05-08 20:37 ` Jens Axboe
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=1525797766.5204.2.camel@gmx.de \
--to=efault@gmx.de \
--cc=axboe@kernel.dk \
--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