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: Sat, 18 Dec 2021 10:28:44 +0000 [thread overview]
Message-ID: <bug-211425-2300-IyVpCSIHIT@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.15.5 |5.15.10
--- Comment #24 from Andreas (icedragon.aw@web.de) ---
In general the blocking bug still occurs until/with the current mainline kernel
version 5.15.10. With kernel 5.15.10 I could observe additionally some new
warnings messages before the "BUG: workqueue ..." errors (like last message)
starting:
[drm] Fence fallback timer expired on ring gfx
[drm] Fence fallback timer expired on ring gfx
BUG: workqueue lockup - pool cpus=7 node=0 flags=0x0 nice=-20 stuck for 47s!
Showing busy workqueues and worker pools:
...
BUT I found a new hardware-patch solution! In my case the monitor accepts only
over the DP-to-DP link connection 4K@60Hz. Over a HDMI-to-HDMI (same computer
and monitor) I got only the 4K@30Hz (not a cable limitation, it is a monitor
limit). But if I connect both cables at the same time, means DP-to-DP 4K@60Hz,
and in addition a HDMI-to-HDMI cable (but this screen connection disabled from
the desktop session control manager) - I could avoid the black screen
completely (without any limitations and stable over reboots)!!!
-> In this double cable configuration (HDMI disabled) the screen (DP
connection) always recovers after some seconds (no hung up and no 2x20sec
delay) - I was not able to trigger the error behaviour any more and I could
also not observe any of the above error messages.
-> But with this stable double cable configuration I observe some new warning
messages (more than one times):
[drm] Unknown EDID CEA parser results
...
Maybe this helps a little bit for progress ... If someone like, I could make
more tests ...
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-12-18 10:28 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
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 [this message]
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-IyVpCSIHIT@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.