[AMD Official Use Only - AMD Internal Distribution Only] I see some errors unrelated to display, like:
[ 361.423085] amdgpu 0000:03:00.0: amdgpu: ring_buffer_start = 00000000bdad4a86; ring_buffer_end = 000000000059d4d9; write_frame = 00000000965e67c9 [ 361.423099] amdgpu 0000:03:00.0: amdgpu: write_frame is pointing to address out of bounds [ 361.423188] amdgpu 0000:03:00.0: amdgpu: ring_buffer_start = 00000000bdad4a86; ring_buffer_end = 000000000059d4d9; write_frame = 00000000965e67c9 [ 361.423190] amdgpu 0000:03:00.0: amdgpu: write_frame is pointing to address out of bounds and [ 361.519801] amdgpu 0000:03:00.0: amdgpu: device lost from bus! [ 361.519814] amdgpu 0000:03:00.0: amdgpu: SMU: response:0xFFFFFFFF for index:36 param:0x00000001 message:SetWorkloadMask? [ 361.519818] amdgpu 0000:03:00.0: amdgpu: Failed to set workload mask 0x00000001 [ 361.519826] amdgpu 0000:03:00.0: amdgpu: (-121) failed to disable fullscreen 3D power profile mode Do you have these errors with the patch reverted? Since the follow up patch did not work, please try partially reverting the culprit patch (the two hunks) to help us pinpoint which one fixes the issue for you? -- Regards, Jay ________________________________ From: Mikhail Gavrilov <[email protected]> Sent: Monday, December 8, 2025 6:34 PM To: Pillai, Aurabindo <[email protected]> Cc: amd-gfx list <[email protected]>; Linux List Kernel Mailing <[email protected]>; Vojvodic, Relja (Reggie) <[email protected]>; Liu, Wenjing <[email protected]>; Deucher, Alexander <[email protected]> Subject: Re: [REGRESSION] Black screen on HDMI power-cycle after commit 3471b9a31ce3 (7900XTX + LG C3) On Tue, Dec 9, 2025 at 1:57 AM Aurabindo Pillai <[email protected]> wrote: > > It is available on amd-staging-drm-next. I'm also attaching here. Let me > know if this helps. Hi Aurabindo, I applied the patch you provided ("drm/amd/display: Improve HDMI info retrieval"), but unfortunately, it does not resolve the issue. The behavior remains exactly the same: the HDMI signal is still lost after power-cycling the TV. I have attached a new dmesg log (captured with drm.debug=0x116) with your patch applied. Hopefully, it shows why the fix didn't work. -- Best Regards, Mike Gavrilov.
