From: Hans de Goede <firstname.lastname@example.org>
To: Bart Van Assche <email@example.com>,
Linux Kernel Mailing List <firstname.lastname@example.org>,
Jens Axboe <email@example.com>
Cc: firstname.lastname@example.org, email@example.com
Subject: Re: 6.0-rc1 regression block (blk_mq) / RCU task stuck errors + block-io hang
Date: Sat, 20 Aug 2022 17:37:40 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 8/19/22 16:49, Bart Van Assche wrote:
> 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://email@example.com/).
Thanks that is very useful. I'm running 6.0-rc1 with this
patch added now and so far I've not seen the problem re-occur.
I was also seeing 6.0 suspend/resume issues on 2 laptops with
sata disks (rather then NVME) which I did not yet get around
to collecting logs from / reporting. I'm happy to report that
those suspend/resume issues are also fixed by this.
I'll reply to the patch with my Tested-by for this.
prev parent reply other threads:[~2022-08-20 15:37 UTC|newest]
Thread overview: 3+ 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 [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).