From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211425] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 20secs aborting
Date: Tue, 30 Mar 2021 19:28:58 +0000 [thread overview]
Message-ID: <bug-211425-2300-Gsa5rX3I9f@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211425-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon.aw@web.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version|5.11.5 |5.11.11
--- Comment #13 from Andreas (icedragon.aw@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.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2021-03-30 19:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 8:29 [Bug 211425] New: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 20secs aborting bugzilla-daemon
2021-01-27 10:30 ` [Bug 211425] " bugzilla-daemon
2021-01-27 21:19 ` bugzilla-daemon
2021-01-27 21:20 ` bugzilla-daemon
2021-02-02 16:41 ` bugzilla-daemon
2021-02-05 8:19 ` bugzilla-daemon
2021-02-09 13:49 ` bugzilla-daemon
2021-02-09 16:55 ` bugzilla-daemon
2021-02-09 21:06 ` bugzilla-daemon
2021-02-13 19:48 ` bugzilla-daemon
2021-02-13 19:48 ` bugzilla-daemon
2021-02-15 15:14 ` bugzilla-daemon
2021-02-16 17:59 ` bugzilla-daemon
2021-02-19 8:50 ` bugzilla-daemon
2021-02-27 17:00 ` bugzilla-daemon
2021-03-06 16:43 ` bugzilla-daemon
2021-03-08 8:13 ` bugzilla-daemon
2021-03-09 19:15 ` bugzilla-daemon
2021-03-30 19:28 ` bugzilla-daemon [this message]
2021-03-30 20:49 ` bugzilla-daemon
2021-03-31 7:40 ` bugzilla-daemon
2021-04-08 9:27 ` bugzilla-daemon
2021-06-23 17:59 ` bugzilla-daemon
2021-06-26 12:11 ` bugzilla-daemon
2021-07-07 7:13 ` bugzilla-daemon
2021-07-21 7:08 ` bugzilla-daemon
2021-07-22 17:40 ` bugzilla-daemon
2021-07-22 17:43 ` bugzilla-daemon
2021-08-01 10:10 ` bugzilla-daemon
2021-08-17 18:21 ` bugzilla-daemon
2021-08-27 18:21 ` bugzilla-daemon
2021-09-13 16:07 ` bugzilla-daemon
2021-09-22 7:02 ` bugzilla-daemon
2021-09-24 15:53 ` bugzilla-daemon
2021-10-20 14:48 ` bugzilla-daemon
2021-10-31 17:00 ` bugzilla-daemon
2021-11-06 10:53 ` bugzilla-daemon
2021-11-27 13:34 ` bugzilla-daemon
2021-12-18 10:28 ` bugzilla-daemon
2022-04-11 0:06 ` bugzilla-daemon
2022-12-21 16:35 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-211425-2300-Gsa5rX3I9f@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.