From: Bart Van Assche <bvanassche@acm.org>
To: Hans de Goede <hdegoede@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: 6.0-rc1 regression block (blk_mq) / RCU task stuck errors + block-io hang
Date: Fri, 19 Aug 2022 07:49:25 -0700 [thread overview]
Message-ID: <17ccd5ae-0268-1bee-7822-1352f4c676ba@acm.org> (raw)
In-Reply-To: <dd6844e7-f338-a4e9-2dad-0960e25b2ca1@redhat.com>
On 8/19/22 05:01, Hans de Goede wrote:
> I've been dogfooding 6.0-rc1 on my main workstation and I have hit
> this pretty serious bug, serious enough for me to go back to 5.19
>
> My dmesg is showing various blk_mq (RCU?) related lockdep splats
> followed by some tasks getting stuck on disk-IO. E.g. "sync"
> is guaranteed to hang, but other tasks too.
>
> This seems to be mainly the case on "sd" disks (both sata
> and USB) where as my main nvme drive seems fine, which has
> probably saved me from worse issues...
>
> Here are 4 task stuck reports from my last boot, where
> I had to turn off the machine by keeping the power button
> pressed for 4 seconds.
>
> [ ... ]
>
> Sorry for not being able to write a better bug-report but I don't have
> the time to dive into this deeper. I hope this report is enough for
> someone to have a clue what is going on.
Thank you for the detailed report. I think this report is detailed
enough to root-cause this issue, something that was not possible before
this report.
Please help with verifying whether this patch fixes this issue: "[PATCH]
scsi: sd: Revert "Rework asynchronous resume support""
(https://lore.kernel.org/linux-scsi/20220816172638.538734-1-bvanassche@acm.org/).
Thanks,
Bart.
next prev parent reply other threads:[~2022-08-19 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 12:01 6.0-rc1 regression block (blk_mq) / RCU task stuck errors + block-io hang Hans de Goede
2022-08-19 14:49 ` Bart Van Assche [this message]
2022-08-20 15:37 ` Hans de Goede
2022-08-23 7:49 ` 6.0-rc1 regression block (blk_mq) / RCU task stuck errors + block-io hang #forregzbot Thorsten Leemhuis
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=17ccd5ae-0268-1bee-7822-1352f4c676ba@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hdegoede@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rcu@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).