From: "Ionut Nechita (Sunlight Linux)" <sunlightlinux@gmail.com>
To: christian.koenig@amd.com
Cc: alexander.deucher@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, ionut_n2001@yahoo.com,
linux-kernel@vger.kernel.org, sunlightlinux@gmail.com,
superm1@kernel.org
Subject: Re: [PATCH 1/1] drm/amdgpu: Fix TLB flush failures after hibernation resume
Date: Mon, 26 Jan 2026 21:40:48 +0200 [thread overview]
Message-ID: <20260126194057.7376-2-sunlightlinux@gmail.com> (raw)
In-Reply-To: <77fa0344-3507-420e-9d77-d454ace55cfd@amd.com>
From: Ionut Nechita <sunlightlinux@gmail.com>
On Thu, Jan 8 2026 at 13:36, Christian König wrote:
> Question is why the KIQ is not up and running before we do anything with it?
Thank you for the feedback. I completely understand that my patch is
just a workaround and not proper engineering - you're absolutely right
that the real issue is KIQ being marked as ready before it's actually
functional.
I don't have experience with GPU drivers and video subsystems, so I'm
not familiar with the proper initialization sequence for KIQ. I'd prefer
not to keep a workaround for this issue in my tree.
Is there a proper fix available, or could you point me in the right
direction? I'm happy to test any patches on my AMD Cezanne (Renoir)
hardware where I can reliably reproduce the issue after hibernation.
Also, regarding hibernation support: you mentioned that hibernation is
not generally supported with the driver. Should I expect other issues
beyond this TLB flush problem, or is this the main blocker?
Thanks for your time,
Ionut
next prev parent reply other threads:[~2026-01-26 19:43 UTC|newest]
Thread overview: 13+ 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) [this message]
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
2026-02-01 19:05 ` 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=20260126194057.7376-2-sunlightlinux@gmail.com \
--to=sunlightlinux@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ionut_n2001@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--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