From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: linux-rt-users@vger.kernel.org
Cc: williams@redhat.com, bigeasy@linutronix.de
Subject: Re: System Hang With 5.15.79-rt54 Patch Set
Date: Wed, 4 Jan 2023 15:47:41 -0500 [thread overview]
Message-ID: <dea6d0e9-7814-4b8c-44dd-4804cbe48227@canonical.com> (raw)
In-Reply-To: <be47fd9c-028a-0b6b-9c7f-877f01e73960@canonical.com>
On 12/15/22 18:39, Joseph Salisbury wrote:
>
>
> On 12/15/22 13:39, Joseph Salisbury wrote:
>> 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
>
> I should have also mentioned, I will also test the latest available
> patch set (6.1-rc7-rt5) to see if it also exhibits the bug.
>
>
This bug/system hang does still happen with the v6.1-rc7 kernel and the
rt5 real-time patch. I also confirmed the bug/system hang does not
happen with just v6.1-rc7 without the real-time patch applied.
I will bisect through the rt patches to see if I can find the specific
patch(s) that causes the bug. I will use the v5.15 kernel and it's rt
patches, since v5.15 has the patches broken out individually, and they
can be applied one at a time with 'git am'.
I'll provide further updates during the bisect.
Thanks,
Joe
next prev parent reply other threads:[~2023-01-04 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 18:39 System Hang With 5.15.79-rt54 Patch Set Joseph Salisbury
2022-12-15 23:39 ` Joseph Salisbury
2023-01-04 20:47 ` Joseph Salisbury [this message]
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=dea6d0e9-7814-4b8c-44dd-4804cbe48227@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).