All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211033] [bisected][regression] amdgpu: *ERROR* Restoring old state failed with -12
Date: Sat, 06 Mar 2021 13:33:24 +0000	[thread overview]
Message-ID: <bug-211033-2300-8706Tg2yHW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211033-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=211033

Jan Klos (honza.klos@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |honza.klos@gmail.com

--- Comment #17 from Jan Klos (honza.klos@gmail.com) ---
I don't think this is limited just to KVMs and such. On my Vega 64 +
5.11.3-arch1 (had the same problem with 5.11.2, 5.10 etc.), sometimes, when I
return to PC after a while and my 2 monitors are sleeping, only one monitor
wakes up, the other one remains in sleep mode. Dmesg shows this:

[bře 6 14:22] [drm] perform_link_training_with_retries: Link training attempt 1
of 4 failed
[bře 6 14:23] [drm] perform_link_training_with_retries: Link training attempt 2
of 4 failed
[  +0,473352] [drm] perform_link_training_with_retries: Link training attempt 3
of 4 failed
[  +0,437753] [drm] enabling link 0 failed: 15
[  +0,432276] [drm] perform_link_training_with_retries: Link training attempt 1
of 4 failed
[  +0,405827] [drm] perform_link_training_with_retries: Link training attempt 2
of 4 failed
[  +0,476172] [drm] perform_link_training_with_retries: Link training attempt 3
of 4 failed
[  +0,415466] [drm] enabling link 1 failed: 15

Switching to terminal and waiting a sec or two makes both monitors work,
switching back to X11 and everything is OK. It seems to me that there might be
some kind of bug where if the first link training attempt fails, the subsequent
ones ALWAYS fail as well, so there is actually only a single actual link
training attempt that has a chance to succeed.

-- 
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

  parent reply	other threads:[~2021-03-06 13:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 17:28 [Bug 211033] New: [bisected][regression] amdgpu: *ERROR* Restoring old state failed with -12 bugzilla-daemon
2021-01-04 17:30 ` [Bug 211033] " bugzilla-daemon
2021-01-04 20:15 ` bugzilla-daemon
2021-01-04 22:23 ` bugzilla-daemon
2021-01-05 10:41 ` bugzilla-daemon
2021-01-05 12:19 ` bugzilla-daemon
2021-01-05 21:15 ` bugzilla-daemon
2021-01-06 17:20 ` bugzilla-daemon
2021-01-06 18:42 ` bugzilla-daemon
2021-01-06 23:48 ` bugzilla-daemon
2021-01-06 23:50 ` bugzilla-daemon
2021-01-11  0:39 ` bugzilla-daemon
2021-01-11 16:51 ` bugzilla-daemon
2021-01-11 16:54 ` bugzilla-daemon
2021-01-11 17:00 ` bugzilla-daemon
2021-01-27  0:10 ` bugzilla-daemon
2021-01-27  1:41 ` bugzilla-daemon
2021-02-04  4:49 ` bugzilla-daemon
2021-03-06 13:33 ` bugzilla-daemon [this message]
2021-03-08 21:48 ` bugzilla-daemon
2023-08-15 17:37 ` 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-211033-2300-8706Tg2yHW@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.