Re: [REGRESSION] AMD GPU regression in 5.16.18..5.17.4

[Demi Marie Obenour <demi@invisiblethingslab.com>]

[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]

On Sun, Apr 24, 2022 at 11:02:43AM +0200, Thorsten Leemhuis wrote:
> CCing the amdgpu maintainers

Also CCing Marek Marczykowski-Górecki as Qubes OS Project Lead.

> On 24.04.22 08:12, Greg KH wrote:
> > On Sat, Apr 23, 2022 at 12:06:33PM -0400, Demi Marie Obenour wrote:
> >> Two Qubes OS users reported that their AMD GPU systems did not work on
> >> 5.17.4, while 5.16.18 worked fine.  Details can be found on
> >> https://github.com/QubesOS/qubes-issues/issues/7462.  The initial report
> >> listed the GPU as “Advanced Micro Devices, Inc. [AMD/ATI] Renoir
> >> [1002:1636} (rev d3) (prog-if 00 [VGA controller])” and the CPU as
> >> “AMD Ryzen 5 PRO 4650U with Radeon Graphics”.
> >>
> >> #regzbot introduced: v5.16.18..v5.17.4
> > 
> > That's a big range, can you use 'git bisect' to track it down?
> 
> FWIW, in another mail in this thread and
> https://github.com/QubesOS/qubes-issues/issues/7462#issuecomment-1107681126
> it was clarified that the problem was introduced between 5.17.3 and
> 5.17.4, where a few amdgpu changes were applied. Maybe they are the reason.

I suspect they are, but I am not certain.  It could also be an
interaction between these changes and running as a PV dom0 under Xen.

> Anyway: Yes, as Gregkh said, a bisection really would help. But maybe
> the amdgfx developers might already have an idea what might be wrong
> here? The QubesOS ticket linked above has some more details.

I can’t provide a bisection myself as I don’t have the hardware.  I
asked the user who reported the bug if they are comfortable doing a
bisection.

-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]