From: Thomas Gleixner <tglx@linutronix.de>
To: "Ostrowski, Rafal" <Rafal.Ostrowski@amd.com>,
Bert Karwatzki <spasswolf@web.de>
Cc: "Varone, Dillon" <Dillon.Varone@amd.com>,
"Hung, Alex" <Alex.Hung@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-rt-devel@lists.linux.dev" <linux-rt-devel@lists.linux.dev>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: kernel panic when resuming from hibernate in next-20260406 with PREEMPT_RT
Date: Wed, 06 May 2026 21:41:20 +0200 [thread overview]
Message-ID: <87ik90wckf.ffs@tglx> (raw)
In-Reply-To: <IA1PR12MB630726FFADF30847A8496012F8362@IA1PR12MB6307.namprd12.prod.outlook.com>
Rafal!
On Mon, Apr 27 2026 at 09:23, Rafal Ostrowski wrote:
> I am glad to hear that mentioned patch fixed your issue.
> Small clarification - amdgpu is not designed to support
> PREEMPT_RT flag, but it was still worth to fix as obvious regression.
PREEMPT_RT is not a flag. It's a valid supported preemption model and
you have to support it whether you like it or not.
Please fix your CI to test with CONFIG_PREEMPT_RT=y so future issues
like that can be avoided.
Thanks,
tglx
next prev parent reply other threads:[~2026-05-07 10:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:14 kernel panic when resuming from hibernate in next-20260406 with PREEMPT_RT Bert Karwatzki
2026-04-09 13:30 ` Ostrowski, Rafal
2026-04-09 13:33 ` Bert Karwatzki
2026-04-09 13:57 ` Ostrowski, Rafal
2026-04-09 19:18 ` Ostrowski, Rafal
2026-04-10 13:20 ` Ostrowski, Rafal
2026-04-26 8:28 ` Bert Karwatzki
2026-04-27 9:23 ` Ostrowski, Rafal
2026-04-27 10:14 ` Sebastian Andrzej Siewior
2026-05-06 19:41 ` Thomas Gleixner [this message]
2026-04-09 13:30 ` Bert Karwatzki
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=87ik90wckf.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Alex.Hung@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Dillon.Varone@amd.com \
--cc=Rafal.Ostrowski@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=spasswolf@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.