From: Bert Karwatzki <spasswolf@web.de>
To: "Ostrowski, Rafal" <Rafal.Ostrowski@amd.com>
Cc: "Varone, Dillon" <Dillon.Varone@amd.com>,
spasswolf@web.de, "Hung, Alex" <Alex.Hung@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@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: Thu, 09 Apr 2026 15:33:57 +0200 [thread overview]
Message-ID: <a67b9159f69e8788a598fb459d8e6d99d1776f2f.camel@web.de> (raw)
In-Reply-To: <IA1PR12MB6307858BAECC7CC3AE8AA958F8582@IA1PR12MB6307.namprd12.prod.outlook.com>
Am Donnerstag, dem 09.04.2026 um 13:30 +0000 schrieb Ostrowski, Rafal:
>
>
>
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Bert,
>
>
> Sorry that you experience this issue.
>
>
> Do you have all these 3 patches?:
> "drm/amd/display: Move FPU Guards From DML To DC - Part 1"
> "drm/amd/display: Move FPU Guards From DML To DC - Part 2"
> "drm/amd/display: Move FPU Guards From DML To DC - Part 3"
>
>
> These are highly dependent on each other.
>
>
> Kind Regards,
> Rafal
>
The crashes also occur when all three patches are applied.
Bert Karwatzki
next prev parent reply other threads:[~2026-04-09 13:34 UTC|newest]
Thread overview: 4+ 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 ` Bert Karwatzki
[not found] ` <IA1PR12MB6307858BAECC7CC3AE8AA958F8582@IA1PR12MB6307.namprd12.prod.outlook.com>
2026-04-09 13:33 ` Bert Karwatzki [this message]
2026-04-09 19:18 ` Ostrowski, Rafal
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=a67b9159f69e8788a598fb459d8e6d99d1776f2f.camel@web.de \
--to=spasswolf@web.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=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox