AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "Ionut Nechita (Sunlight Linux)" <sunlightlinux@gmail.com>,
	alexdeucher@gmail.com
Cc: alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
	christian.koenig@amd.com, dri-devel@lists.freedesktop.org,
	ionut_n2001@yahoo.com, linux-kernel@vger.kernel.org,
	superm1@kernel.org
Subject: Re: [PATCH 1/1] drm/amdgpu: Fix TLB flush failures after hibernation resume
Date: Tue, 27 Jan 2026 12:35:06 +0100	[thread overview]
Message-ID: <7f049afd-b2d0-4369-af9a-416abed500fa@amd.com> (raw)
In-Reply-To: <20260126203749.16389-2-sunlightlinux@gmail.com>

Hi Ionut,

On 1/26/26 21:37, Ionut Nechita (Sunlight Linux) wrote:
> Hi Alex,
> 
> Thank you for the feedback and for taking the time to review this issue.
> 
> I'll add debug code to capture the full stack trace when the TLB flush
> failures occur. I'll test this on my AMD Cezanne system over the next
> few days when I have more time available, and will send you the complete
> call chain information.
> 
> Regarding the hibernation limitations you mentioned - I understand the
> challenges with secure boot compatibility and VRAM eviction. In my case,
> I'm not using secure boot, and my system has sufficient RAM and swap
> space to handle the VRAM backup, so those particular issues shouldn't
> affect my setup.

the problem is since the AMD GPU doesn't official support hibernation you are pretty much the only one able to reproduce the bug.

In other words I can't go to my manager to get a Cezanne system plus time to work on this.

What Alex, Mario, I and all the other devs can do is to explain to you how the driver works and try to further debug what's going on here.

> I'll follow up with the stack traces and additional debugging information
> in the next few days.

That would certainly be helpful.

Thanks,
Christian.

> 
> Thanks again,
> Ionut


  reply	other threads:[~2026-01-27 11:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 12:59 [PATCH 0/1] drm/amdgpu: Fix TLB flush failures after hibernation resume Ionut Nechita (Sunlight Linux)
2026-01-06 12:59 ` [PATCH 1/1] " Ionut Nechita (Sunlight Linux)
2026-01-06 16:26   ` Alex Deucher
2026-01-07 10:52     ` Ionut Nechita (Sunlight Linux)
2026-01-08 12:36   ` Christian König
2026-01-26 19:40     ` Ionut Nechita (Sunlight Linux)
2026-01-26 20:25       ` Alex Deucher
2026-01-26 20:28         ` Mario Limonciello (AMD) (kernel.org)
2026-01-26 20:32           ` Mario Limonciello (AMD) (kernel.org)
2026-01-26 20:46             ` Ionut Nechita (Sunlight Linux)
2026-01-26 20:37         ` Ionut Nechita (Sunlight Linux)
2026-01-27 11:35           ` Christian König [this message]
2026-02-01 19:05         ` Ionut Nechita (Sunlight Linux)
2026-02-02 10:39           ` Christian König
2026-03-24  8:07             ` Ionut Nechita (Sunlight Linux)

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=7f049afd-b2d0-4369-af9a-416abed500fa@amd.com \
    --to=christian.koenig@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ionut_n2001@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sunlightlinux@gmail.com \
    --cc=superm1@kernel.org \
    /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