All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105188] Monitors don't always wake up after sleep
Date: Wed, 21 Feb 2018 11:17:12 +0000	[thread overview]
Message-ID: <bug-105188-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1774 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105188

            Bug ID: 105188
           Summary: Monitors don't always wake up after sleep
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: mbartoszkiewicz@gmail.com

Created attachment 137497
  --> https://bugs.freedesktop.org/attachment.cgi?id=137497&action=edit
Kernel log

Hardware:
 GPU: Gigabyte Radeon RX 480 G1 Gaming 8GB
 Monitors: 3× Eizo FlexScan S2243W, connected using DP
Software:
 Distribution: Gentoo
 Kernel: 4.15.4
 x11-drivers/xf86-video-amdgpu-1.4.0
 x11-base/xorg-server-1.19.6
 media-libs/mesa-18.0.0_rc4
 x11-libs/libdrm-2.4.89

The monitors do not always correctly wake up from sleep.
E.g. after locking the session, the monitors go to sleep.
After pressing a key, only some wake up – the rest are still sleeping.
It does not seem to be deterministic – sometimes a monitor will wake up
correctly, sometimes not.

The kernel log attached is after running the following script:
for i in {1..5}; do echo "XXX before suspend $i" | sudo tee /dev/kmsg; xset
dpms force suspend; sleep 10; echo "XXX before on $i" | sudo tee /dev/kmsg;
xset dpms force on; sleep 10; echo "XXX status $i:" $(cat
/sys/devices/pci0000:00/0000:00:03.0/0000:03:00.0/drm/card0/card0-DP-*/status)
| sudo tee /dev/kmsg; done

I am not sure if it is directly related to this issue, but the kernel log
contains two refcount_t warnings in amdgpu code.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3205 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-02-21 11:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 11:17 bugzilla-daemon [this message]
2018-02-21 11:18 ` [Bug 105188] Monitors don't always wake up after sleep bugzilla-daemon
2018-02-21 16:31 ` bugzilla-daemon
2018-02-21 17:39 ` bugzilla-daemon
2019-11-19  8:30 ` 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-105188-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.