From: Thorsten Leemhuis <linux@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: 6.0-rc1 regression block (blk_mq) / RCU task stuck errors + block-io hang #forregzbot
Date: Tue, 23 Aug 2022 09:49:45 +0200 [thread overview]
Message-ID: <19c01d05-4bcd-dd03-7104-a6075f037f7b@leemhuis.info> (raw)
In-Reply-To: <dd6844e7-f338-a4e9-2dad-0960e25b2ca1@redhat.com>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 19.08.22 14:01, Hans de Goede wrote:
> Hi All,
>
> 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.
Just for the record:
#regzbot introduced: v5.19..v6.0-rc1
#regzbot dup-of:
https://lore.kernel.org/all/98592410-dd31-9081-86be-fda67d3b06d2@suse.cz/
Ciao, Thorsten
prev parent reply other threads:[~2022-08-23 7: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
2022-08-20 15:37 ` Hans de Goede
2022-08-23 7:49 ` Thorsten Leemhuis [this message]
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=19c01d05-4bcd-dd03-7104-a6075f037f7b@leemhuis.info \
--to=linux@leemhuis.info \
--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).