From: Mike Galbraith <efault@gmx.de>
To: Paolo Valente <paolo.valente@linaro.org>, Jens Axboe <axboe@kernel.dk>
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 10:37:12 +0200 [thread overview]
Message-ID: <1525768632.5208.4.camel@gmx.de> (raw)
In-Reply-To: <1525755090.24338.1.camel@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
On Tue, 2018-05-08 at 06:51 +0200, Mike Galbraith wrote:
>
> I'm deadlined ATM, but will get to it.
(Bah, even a zombie can type ccache -C; make -j8 and stare...)
kbuild again hung on the first go (yay), and post hang data written to
sdd1 survived (kernel source lives in sdb3). Full ftrace buffer (echo
1 > events/block/enable) available off list if desired. dmesg.txt.xz
is dmesg from post hang crashdump, attached because it contains the
tail of trace buffer, so _might_ be useful.
homer:~ # df|grep sd
/dev/sdb3 959074776 785342824 172741072 82% /
/dev/sdc3 959074776 455464912 502618984 48% /backup
/dev/sdb1 159564 7980 151584 6% /boot/efi
/dev/sdd1 961301832 393334868 519112540 44% /abuild
Kernel is virgin modulo these...
patches/remove_irritating_plus.diff
patches/add-scm-version-to-EXTRAVERSION.patch
patches/block-bfq:-postpone-rq-preparation-to-insert-or-merge.patch
patches/block-bfq:-test.patch (hang provocation hack from Paolo)
-Mike
[-- Attachment #2: block_debug.tar.xz --]
[-- Type: application/x-xz-compressed-tar, Size: 2292 bytes --]
[-- Attachment #3: dmesg.xz --]
[-- Type: application/x-xz, Size: 17300 bytes --]
[-- Attachment #4: dmesg.txt.xz --]
[-- Type: application/x-xz, Size: 15824 bytes --]
next prev parent reply other threads:[~2018-05-08 8:37 UTC|newest]
Thread overview: 24+ 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 14:03 ` Paolo Valente
2018-05-07 16:39 ` Jens Axboe
2018-05-07 18:02 ` Paolo Valente
2018-05-07 18:02 ` Paolo Valente
2018-05-08 4:51 ` Mike Galbraith
2018-05-08 4:51 ` Mike Galbraith
2018-05-08 8:37 ` Mike Galbraith [this message]
2018-05-08 14:55 ` Jens Axboe
2018-05-08 14:55 ` Jens Axboe
2018-05-08 16:42 ` Mike Galbraith
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 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=1525768632.5208.4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.