All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 23 Jun 2021 17:59:18 +0000	[thread overview]
Message-ID: <bug-211425-2300-KtPke4NZRj@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.12                     |5.12.12
           Severity|normal                      |high

--- Comment #17 from Andreas (icedragon.aw@web.de) ---
At least since kernel 5.12.11 I have a chance (not 100% reproducible) that the
screen does not recover! 

Keyboard partially not disabled, e.g. num-lock and caps-lock not working, but
magic SysRq key shortcuts still working.

Here are the last kernel messages (5.12.12) after the screens keeps black (did
not recover).:

Jun 23 19:31:24 localhost kernel: [255985.517110] [drm]
perform_link_training_with_retries: Link training attempt 1 of 4 failed
Jun 23 19:31:45 localhost kernel: [256006.097054] [drm:atom_op_jump] *ERROR*
atombios stuck in loop for more than 20secs aborting
Jun 23 19:31:45 localhost kernel: [256006.097061]
[drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing B228
(len 3608, WS 8, PS 0) @ 0xB376
Jun 23 19:31:45 localhost kernel: [256006.097064]
[drm:amdgpu_atom_execute_table_locked] *ERROR* atombios stuck executing B11C
(len 268, WS 4, PS 0) @ 0xB16F
Jun 23 19:31:45 localhost kernel: [256006.097067]
[drm:dcn10_link_encoder_enable_dp_output] *ERROR*
dcn10_link_encoder_enable_dp_output: Failed to execute VBIOS command table!
Jun 23 19:31:45 localhost kernel: [256006.108713] [drm]
perform_link_training_with_retries: Link training attempt 2 of 4 failed

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

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

  parent reply	other threads:[~2021-06-23 17:59 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 [this message]
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-KtPke4NZRj@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.