Comme=
nt # 19
on bug 10920=
6
from Tim Carr
(In reply to Harry Wentland from comment #15)
> Can you see if this patch fixes it:
> https://pa=
tchwork.freedesktop.org/patch/277181/
Wasn't able to get that patch to apply cleanly to either 4.20 or 5.0rc2. I =
did
attempt to manually edit the function in the amdgpu_psp.c file according to=
the
patch, but now have in my log:
"[drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectI=
D from
Adapter Service for connector index:2! type 0 expected 3"=20
I'm assuming I attempted to apply the patch to the wrong revision. Behavior=
for
me is somewhat changed, before the patch I got about 4 lines of scrambled
pixels about 4/5ths of the way down my screen on anything above kernel 4.19,
with the patch applied to 5.0rc2 those lines appear for a couple of seconds=
and
then the screen goes and remains totally blank.
I can attach the full log if you want, but considering I wasn't able to
directly apply the patch and instead manually modified the "psp_cmd_su=
bmit_buf"
function to warn instead of error and not return -EINVAL as described in the
patch, I'd rather not clutter this with potentially bad log data. Should th=
at
patch be applied to drm-next instead of what is in the mainline kernel?