From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: linux-rt-users@vger.kernel.org
Cc: williams@redhat.com, bigeasy@linutronix.de
Subject: System Hang With 5.15.79-rt54 Patch Set
Date: Thu, 15 Dec 2022 13:39:38 -0500 [thread overview]
Message-ID: <fe5974c9-3ed0-938a-f43c-4d301f603e92@canonical.com> (raw)
Hello,
A bug has been reported[0] against a linux-5.15.y based Ubuntu kernel
that has the 5.15.79-rt54 real-time patch set applied.
This bug is causing a system hang when running disk tests with the
stress-ng[1] test suite. A 'hung task' call trace is being generated[2]
just prior to the system hanging. It appears the hang is happening
during a call to schedule.
To see if this was a regression, I also tested prior real-time patch
sets, going as far back to rt38 and all versions exhibit this bug. I
will test back further to see if this is in fact a regression and a
kernel bisect can be done. I also confirmed the same kernel without the
rt54 patch set applied does not exhibit this bug.
I will continue to debug this issue, but I wanted to send this message
upstream in case anyone else runs into it. Any specific tests, tracing
or debugging steps would be greatly appreciated. Otherwise, I'll report
back to this thread with any findings.
Thanks,
Joe
[0] https://bugs.launchpad.net/ubuntu-realtime/+bug/1998536
[1] https://github.com/ColinIanKing/stress-ng
[2] https://launchpadlibrarian.net/637058129/dmesg_dl110_rt_kernel.txt
next reply other threads:[~2022-12-15 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 18:39 Joseph Salisbury [this message]
2022-12-15 23:39 ` System Hang With 5.15.79-rt54 Patch Set Joseph Salisbury
2023-01-04 20:47 ` Joseph Salisbury
2023-01-18 18:52 ` Joseph Salisbury
2023-02-16 17:15 ` Sebastian Andrzej Siewior
2023-03-10 21:09 ` Joseph Salisbury
2023-03-13 15:11 ` Alison Chaiken
2023-02-28 16:50 ` Joseph Salisbury
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=fe5974c9-3ed0-938a-f43c-4d301f603e92@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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).