| Summary: | Monitors don't always wake up after sleep | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Michał Bartoszkiewicz <mbartoszkiewicz> | ||||||
| Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||||
| Status: | RESOLVED MOVED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | bugs.freedesktop.org, FD, harry.wentland | ||||||
| Version: | unspecified | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
Created attachment 137498 [details]
Kernel configuration
Are the monitors set to DP input or to auto-scan the inputs? We've seen similar issues with some monitors that auto-scan inputs and disappear on us when we try to enable them. The monitors are set to DP input, auto-scan is disabled. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/310. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 137497 [details] 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.