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: Tue, 05 Jan 2021 10:41:56 +0000	[thread overview]
Message-ID: <bug-211033-2300-Wnlh3CViw1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211033-2300@https.bugzilla.kernel.org/>

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

Jindrich Makovicka (makovick@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |makovick@gmail.com

--- Comment #3 from Jindrich Makovicka (makovick@gmail.com) ---
On Tue, 5 Jan 2021 07:54:02 +0100, Greg Kroah-Hartman wrote:

> Can you test 5.11-rc to see if this issue is there as well?

Tested with 5.11.0-rc2 and 5600 XT, same issue.

"xset dpms force off" turns the display off and it won't come back,
with the same error in the syslog.

Jan  5 11:11:54 holly kernel: [drm:dm_restore_drm_connector_state
[amdgpu]] *ERROR* Restoring old state failed with -12

Can be worked around by

1) turning display power off completely
2) switching to console
3) turning display power on - linux console shows up
4) switching back to X

-- 
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-01-05 10:41 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 [this message]
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
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-Wnlh3CViw1@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.