[Bug 211425] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 20secs aborting

[bugzilla-daemon at bugzilla.kernel.org]

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

Andreas (icedragon.aw at web.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Kernel Version|5.11.5                      |5.11.11

--- Comment #13 from Andreas (icedragon.aw at web.de) ---
I have make a comparison with a second full AMD System:
A) Ryzen 7 PRO 4750G APU (with build in Vega20) - Renoir
B) Ryzen Threadripper 1900X with dedicated Vega64 GPU
Both systems have installed the same OS (Kubuntu 20.10 with latest updates),
same Xorg configuration (because both have a Vega-GPU), same User IO (monitor,
keyboard and mouse) and running with the same mainline Kernel 5.11.11 (similar
.config file).

- Only my System A) is reproducible infected with the atombios errors (see
comments above) and with the two times monitor blackout of each 20sec - after
triggering the issue with simple putting the monitor off and on again (after
waiting some seconds).

- Because both systems have a vega gpu and using the same driver - it seem to
be a Renoir APU only problem.

- I also observed, that the issue can not be triggered (or is very hard to
reproduce) during the sddm login screen! It seems to be, that only a regular
KDE user or root session (inclusive the lock screen from a session) is affected
by the issue.
-> What is the difference? The usage of opengl or other 3d accelerations? I'm
also tested with switching the rendering during a session, but I could not
observe any difference whatever I used (opengl 2.0, 3.2 or xrendering).

>From now I'll only update the bug header for the latest tested (released)
kernel version/subversion.

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

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