[Bug 220906] Regression: 4K display output fails on ThinkPad Thunderbolt 4 Dock with AMD GPU (Worked in 6.17.1, broken in 6.17.11)

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220906

Andrei (danandrei@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|ANSWERED                    |---

--- Comment #6 from Andrei (danandrei@gmail.com) ---
I also checked 6.18.2, it still exhibits the issue. I went through minor
versions between 6.17.1 and 6.17.11, and found the version where the issue was
first introduced.

6.17.4 - works
6.17.5 - works
6.17.6 - does not work

One extra note:

I see the amdgpu line that I originally thought associated the problem, also
appears in the dmesg output for working kernel versions.

For example, 6.17.4 (working):

[    6.602684] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5
[    6.612716] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5
[    6.634430] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5
[    6.639137] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5

6.17.5 (working):

[    6.468886] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5
[    6.473641] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5
[    6.479753] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5
[    6.492847] amdgpu 0000:c3:00.0: amdgpu: [drm] DMUB HPD RX IRQ callback:
link_index=5

The following may or may not be relevant, but here's something that appears
only in problematic versions, and is missing from working versions:

6.17.6:

[   18.911013] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 6935 (idx
101 out of bounds)
[   18.986136] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 7015 (idx
101 out of bounds)
[   19.061037] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 7095 (idx
101 out of bounds)
[   20.562028] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 6435 (idx
101 out of bounds)

6.17.12:

[   34.459370] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 6455 (idx
101 out of bounds)
[   34.534471] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 6535 (idx
101 out of bounds)
[   34.609497] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 6615 (idx
101 out of bounds)
[   34.684571] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 6695 (idx
101 out of bounds)

6.18.2:

[   14.236205] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 5180 (idx
101 out of bounds)
[   14.391215] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 5200 (idx
101 out of bounds)
[   14.546169] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 5220 (idx
101 out of bounds)
[   14.700826] ath12k_pci 0000:c2:00.0: chan info: invalid frequency 5240 (idx
101 out of bounds)

In working versions, ath12k_pci logging terminates with the following:

6.17.1:

[   38.914023] ath12k_pci 0000:c2:00.0: failed to enqueue rx buf: -28

6.17.4:

[   37.071153] ath12k_pci 0000:c2:00.0: failed to enqueue rx buf: -28

6.17.5:

[    6.586797] ath12k_pci 0000:c2:00.0: failed to enqueue rx buf: -28

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.