Comment # 16 on bug 1179925 from
(In reply to Takashi Iwai from comment #15)
> OK, that's what I was afraid of; for fixing this, we'd need backport tons of
> patches, as this is rather a new GPU model (Raven2 or such), and another GPU
> reset model is needed that needs another infrastructure in amdgpu, etc, etc.

The laptop is not really that recent, it was released on May 2019, it works
fine with 5.4.62 (lowest version I've tried in the 5.4.x series that gave me no
issues at all with the GPU).

In an ideal world, one could just drop the new amdgpu drm code that contains
support for new GPUs and important fixes for older ones, compile it and use it,
but the drm subsystem kpi constant changes makes it hard/impossible.

I do also perfectly understand the issue with the amdgpu code, it is improving,
but fixes are mixed with new features, which makes the backporting work hard. 

BTW I had other artifacts/issues related to the GPU with version
5.3.18-lp152.57-default, so I would just say that my GPU is not well supported,
and If you agree, I would close this as a feature request.


You are receiving this mail because: