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, 13 Feb 2021 19:48:09 +0000 [thread overview]
Message-ID: <bug-211425-2300-AI1utxHNDY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211425-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211425
--- Comment #7 from Andreas (icedragon.aw@web.de) ---
OK, I could successfully bisect the right point.
- last good kernel version was 5.8.18 (latest 5.8.)
- first bad kernel version was 5.9.0 until latest 5.10.16!
On the kernel 5.4 until 5.8.18 I could only get the 'warnings' like:
[Sa Feb 13 20:37:08 2021] [drm] Failed to add display topology, DTM TA is not
initialized.
-> with kernel prior to and with 5.8.18 no real issue with resuming the screen
(only the topology message above).
Since 5.9.0:
Feb 13 20:33:53 localhost kernel: [ 16.924598] [drm] Failed to add display
topology, DTM TA is not initialized.
Feb 13 20:33:53 localhost kernel: [ 71.826161] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 20secs aborting
Feb 13 20:33:53 localhost kernel: [ 71.826168]
[drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing B200
(len 3615, WS 8, PS 0) @ 0xB34E
Feb 13 20:33:53 localhost kernel: [ 71.826172]
[drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing B0F4
(len 268, WS 4, PS 0) @ 0xB147
Feb 13 20:33:53 localhost kernel: [ 71.826178]
[drm:dcn10_link_encoder_enable_dp_output] *ERROR*
dcn10_link_encoder_enable_dp_output: Failed to execute VBIOS command table!
Feb 13 20:33:54 localhost kernel: [ 73.389814] [drm]
amdgpu_dm_irq_schedule_work FAILED src 2
Also the current latest 5.10.16 produces the errors:
Feb 13 17:41:21 localhost kernel: [ 92.580071] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 20secs aborting
Feb 13 17:41:21 localhost kernel: [ 92.580079]
[drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing B200
(len 3615, WS 8, PS 0) @ 0xB34E
Feb 13 17:41:21 localhost kernel: [ 92.580083]
[drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing B0F4
(len 268, WS 4, PS 0) @ 0xB147
Feb 13 17:41:21 localhost kernel: [ 92.580089]
[drm:dcn10_link_encoder_enable_dp_output] *ERROR*
dcn10_link_encoder_enable_dp_output: Failed to execute VBIOS command table!
Feb 13 17:41:23 localhost kernel: [ 94.143214] [drm]
amdgpu_dm_irq_schedule_work FAILED src 2
--
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-02-13 19:48 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 [this message]
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
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-AI1utxHNDY@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.