linux-kernel - Please Apply: Revert "drm/amd/display: Fix green screen issue after suspend"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <13267282-2b5d-4a9d-aa0e-bbf650ea2221@aosc.io>
Date: Sun, 9 Feb 2025 23:33:55 +0800
From: Mingcong Bai <jeffbai@...c.io>
To: stable@...r.kernel.org
Cc: Harry Wentland <harry.wentland@....com>, Leo Li <sunpeng.li@....com>,
 Rodrigo Siqueira <Rodrigo.Siqueira@....com>,
 Alex Deucher <alexander.deucher@....com>,
 Christian König <christian.koenig@....com>,
 Xinhui Pan <Xinhui.Pan@....com>, David Airlie <airlied@...il.com>,
 Simona Vetter <simona@...ll.ch>, Tom Chung <chiahsuan.chung@....com>,
 Aurabindo Pillai <aurabindo.pillai@....com>, Alex Hung <alex.hung@....com>,
 Sunil Khatri <sunil.khatri@....com>, Hamza Mahfooz <hamza.mahfooz@....com>,
 amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
 linux-kernel@...r.kernel.org, harico@...ier.net,
 Kexy Biscuit <kexybiscuit@...c.io>
Subject: Please Apply: Revert "drm/amd/display: Fix green screen issue after
 suspend"

The display on Lenovo Xiaoxin Pro 13 2019 (Lenovo XiaoXinPro-13API 2019) 
briefly shows a garbled screen upon wakeup from S3 with kernel v6.13.2, 
but not with v6.14-rc1. I have bisected to 
04d6273faed083e619fc39a738ab0372b6a4db20 ("Revert "drm/amd/display: Fix 
green screen issue after suspend"") as the fix to this issue.

However, it is quite strange that the title indicated a revert to the 
fix for the exact issue I was experiencing - despite the commit claiming 
that the maintainers "cannot see the issue" any more. It seems that I'm 
running into some sort of unexpected issue that is outside of AMD's test 
case.

In any case, this commit fixes the issue on the device I have tested and 
applies cleanly on 6.13. I would therefore like to request for this 
commit to be backported to 6.13 (and maybe other branches, but I think 
the maintainers may have a better idea on this).

Reported-By: Yang Wu <harico@...ier.net>
Tested-by: Yang Wu <harico@...ier.net>
Suggested-by: Mingcong Bai <jeffbai@...c.io>