From: bugzilla-daemon@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: Mon, 11 Apr 2022 00:06:18 +0000 [thread overview]
Message-ID: <bug-211425-2300-w23VhEDc8b@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211425-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211425
barnoid@gmx.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barnoid@gmx.net
--- Comment #25 from barnoid@gmx.net ---
I have observed this as well on a 5.15.32 kernel. The system is equipped with
an AMD Threadripper 3970X and 2 x LG HDMI displays connected via DP (4K@60Hz).
The error happens when powering-up the monitors after a long power-down period.
>[122427.564568] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
>[122427.603599] amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
>[122427.954560] [drm] fb mappable at 0xC0E00000
>[122427.954563] [drm] vram apper at 0xC0000000
>[122427.954563] [drm] size 33177600
>[122427.954564] [drm] fb depth is 24
>[122427.954564] [drm] pitch is 15360
>[122427.954625] fbcon: amdgpudrmfb (fb0) is primary device
>[122427.954759] Console: switching to colour frame buffer device 480x135
>[122427.954763] amdgpu 0000:03:00.0: [drm] fb0: amdgpudrmfb frame buffer
>device
>[122482.729791] [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for
>>more than 20secs aborting
>[122482.729839] [drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR*
>atombios stuck executing C220 (len 62, WS 0, PS 0) @ 0xC23C
Ctrl-Alt-F1 and restarting X (i.e., the login manager) is sufficient to bring
the system back into a useable state.
--
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:[~2022-04-11 0:06 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
2022-04-11 0:06 ` bugzilla-daemon [this message]
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-w23VhEDc8b@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.