From: Jens Axboe <axboe@kernel.dk>
To: David Zarzycki <dave@znu.io>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: Hard LOCKUP on 4.15-rc9 + 'blkmq/for-next' branch
Date: Mon, 22 Jan 2018 16:34:16 -0700 [thread overview]
Message-ID: <78e10971-611e-8dd7-104e-8266c3ba3b5c@kernel.dk> (raw)
In-Reply-To: <95E75EBE-D01A-4236-8762-FF3522D6DBAD@znu.io>
On 1/22/18 4:31 PM, David Zarzycki wrote:
> Hello,
>
> I previously reported a hang when building LLVM+clang on a block multi-queue device (NVMe _or_ loopback onto tmpfs with the ’none’ scheduler).
>
> I’ve since updated the kernel to 4.15-rc9, merged the ‘blkmq/for-next’ branch, disabled nohz_full parameter (used for testing), and tried again. Both NVMe and loopback now lock up hard (ext4 if it matters). Here are the backtraces:
>
> NVMe: http://znu.io/IMG_0366.jpg
> Loopback: http://znu.io/IMG_0367.jpg
I tried to reproduce this today using the exact recipe that you provide,
but it ran fine for hours. Similar setup, nvme on a dual socket box
with 48 threads.
> What should I try next to help debug this?
This one looks different than the other one. Are you sure your hw
is sane? I'd probably try and enable lockdep debugging etc and
see if you catch anything.
--
Jens Axboe
next prev parent reply other threads:[~2018-01-22 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 23:31 Hard LOCKUP on 4.15-rc9 + 'blkmq/for-next' branch David Zarzycki
2018-01-22 23:34 ` Jens Axboe [this message]
2018-01-23 1:05 ` David Zarzycki
2018-01-23 1:20 ` Jens Axboe
2018-01-23 13:48 ` David Zarzycki
2018-01-23 15:34 ` Jens Axboe
2018-01-23 17:54 ` David Zarzycki
2018-01-23 18:00 ` Jens Axboe
2018-01-23 18:12 ` David Zarzycki
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=78e10971-611e-8dd7-104e-8266c3ba3b5c@kernel.dk \
--to=axboe@kernel.dk \
--cc=dave@znu.io \
--cc=linux-block@vger.kernel.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