dri-devel Archive on 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: Wed, 06 Jan 2021 17:20:38 +0000	[thread overview]
Message-ID: <bug-211033-2300-4ySUgxF3Lo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211033-2300@https.bugzilla.kernel.org/>

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

Shlomo (shlomo@fastmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |shlomo@fastmail.com

--- Comment #6 from Shlomo (shlomo@fastmail.com) ---
I think I have the same bug on Arch after upgrading linux from 5.10.3.arch1-1
to 5.10.4.arch2-1.

My graphics card is Gigabyte Radeon RX VEGA 56 GAMING OC 8G, connected to 6
monitors: 3 HDMI outputs + 3 DisplayPort outputs. (One of the DisplayPort
outputs is connected to a DisplayPort->HDMI converter). No KVM.
All monitors run at 59.95 or 60 Hz.

Sometimes when I try to wake up the monitors, the 3 monitors on the HDMI
outputs (or occasionally just 1 or 2 of them) don't turn back on. dmesg shows:

[   56.906065] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring
old state failed with -12
[   56.936004] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring
old state failed with -12
[   56.976021] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring
old state failed with -12
[   62.646390] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring
old state failed with -12
[   62.671813] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring
old state failed with -12
[   62.697193] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring
old state failed with -12

The DisplayPort outputs work fine.

Sometimes all monitors correctly turn on, but dmesg shows the following errors
which didn't appear before:

[  542.425462] [drm:dce110_enable_timing_synchronization [amdgpu]] *ERROR* GSL:
Timeout on reset trigger!
[  542.592191] [drm:dce110_enable_timing_synchronization [amdgpu]] *ERROR* GSL:
Timeout on reset trigger!
[  542.937936] [drm:dce110_enable_timing_synchronization [amdgpu]] *ERROR* GSL:
Timeout on reset trigger!
[  543.104672] [drm:dce110_enable_timing_synchronization [amdgpu]] *ERROR* GSL:
Timeout on reset trigger!
[  543.421457] [drm:dce110_enable_timing_synchronization [amdgpu]] *ERROR* GSL:
Timeout on reset trigger!
[  543.588188] [drm:dce110_enable_timing_synchronization [amdgpu]] *ERROR* GSL:
Timeout on reset trigger!
[  543.771657] [drm:dce110_enable_timing_synchronization [amdgpu]] *ERROR* GSL:
Timeout on reset trigger!

ea64b21c6638d1ac3120fff89eb20c0e525a21d9 "drm/amd/display: Fix memory leaks in
S3 resume" is the first bad commit.

-- 
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-06 17:20 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 [this message]
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-4ySUgxF3Lo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox