ACK: [SRU][Q][PATCH 0/1] Fix xe GPU suspend/resume crash on Battlemage
Austin Rhodes
austin.rhodes at canonical.com
Thu Feb 26 20:47:01 UTC 2026
On 2/10/26 04:18, Aaron Ma wrote:
> BugLink: https://bugs.launchpad.net/bugs/2141377
>
> [ Impact ]
> Intel Battlemage xe GPU (8086:e212) crashes during system resume with
> NULL pointer dereference in xe_guc_ads_populate_post_load(), making
> suspend/resume non-functional on affected systems.
>
> Root cause: Noble 6.17 kernels have commit 59cebf0bdff48 but are missing
> its prerequisite commit 1313351e71181. Without proper forcewake handling,
> MMIO register access causes hardware corruption.
>
> [ Fix ]
> Cherry-pick upstream commit from v6.18-rc1:
> - 1313351e71181 ("drm/xe: make xe_gt_idle_disable_c6() handle the forcewake internally")
>
> [ Test Plan ]
> 1. System: Lenovo ThinkStation P3 Ultra G2 with Battlemage dGPU (8086:e212)
> 2. Reproduce: rtcwake -m mem -s 10
> 3. Verify: System resumes successfully without crashes
>
> [ Where problems could occur ]
> It may break xe driver GT idle/power management, affects suspend/resume path.
> Commit is from mainline v6.18-rc1.
>
> The dGPU is not fully certified on v6.8 kernel, so SRU for questing and oem-6.17.
>
Acked-by: Austin Rhodes <austin.rhodes at canonical.com>
More information about the kernel-team
mailing list