Hi Bart,

I can do [1] and [2] but I won=E2=80=99t be able to provide the command =
output because the hang is almost total. No new commands can run because =
the scheduler is hung. For example, see this backtrace:

http://znu.io/IMG_0362.jpg

Is there another approach I can use?

Dave

On Jan 21, 2018, at 12:17, Bart Van Assche [off-list ref] =

wrote:

=20
On Sun, 2018-01-21 at 11:19 -0500, David Zarzycki wrote:

quoted

How can I help debug this further?

=20
Please apply patch [1] on top of Jens' for-next branch [2], reproduce =

the

hang and provide the output of the following command:
=20
(cd /sys/kernel/debug/block && find . -type f -exec grep -aH . {} \;)
=20
Thanks,
=20
Bart.
=20
[1] [PATCH] blk-mq-debugfs: Also show requests that have not yet been =

started

https://www.mail-archive.com/linux-block@vger.kernel.org/msg17313.html
[2] http://git.kernel.dk/cgit/linux-block/log/?h=3Dfor-next