| Bug ID | 110117 |
|---|---|
| Summary | Waking from Suspend causes screen to appear with grey static = (like a TV with no signal) |
| Product | DRI |
| Version | XOrg git |
| Hardware | Other |
| OS | All |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | stein12c@gmail.com |
Created attachment 143671 [details] journalctl -b -1 -k I am running Ubuntu 18.10. This is the PH517-61 Acer Predator Helios 500 wi= th the Ryzen processor. I have temporarily disabled suspend. If I do let the laptop suspend and then hit the keyboard I get what appears to be a TV with= no signal. At this point I manually power down and then power up again and am = able to view things on screen. I have reported this downstream here: ht= tps://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813820 in log.txt I have attached the output of 'journalctl -b -1 -k' uname -a: 5.0.2-050002-generic #201903131832 SMP Wed Mar 13 22:35:19 UTC 20= 19 x86_64 x86_64 x86_64 GNU/Linux Loaded newer kernel from this source: https://= kernel.ubuntu.com/~kernel-ppa/mainline/v5.0.2/ This is a Vega 56 card but here is what I get with this command: lspci -k | grep -EA3 'VGA|3D|Display' 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] V= ega 10 XT [Radeon RX Vega 64] (rev c7) Subsystem: Acer Incorporated [ALI] Vega 10 XT [Radeon RX Vega 64] Kernel driver in use: amdgpu Kernel modules: amdgpu glxinfo | grep "OpenGL version" OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.2 Expected Behaviour: I expect to continue to be able to use my machine normally and be able to s= ee what is happening on screen. Actual Behaviour: Static on screen obscures everything.
| What | Removed | Added |
|---|---|---|
| Hardware | Other | x86-64 (AMD64) |
| OS | All | Linux (All) |
| Priority | medium | high |
I don't see anything immediately wrong in the log at the first= glance at least so it'd be helpful if you could post your dmesg log from after the problem occurred with drm.debug=3D4 in your kernel boot parameters. Please post your xorg log if applicable as well.
Steps I took: 1. added drm.debug=3D4 to /etc/default/grub 2. sudo update-grub 3. reboot 4. reproduced the issue 5. rebooted using ctrl-sysrq-reisub 6. dumped this dmesg into log.txt
Created attachment 143692 [details]
dmesg after reproducing issue and rebooting
Created attachment 143693 [details]
dmesg where i ssh'd into machine during the screen static
Created attachment 143698 [details]=
Xorg Log around the recreation of the problem
Created attachment 143699 [details]=
Xorg.old log when the error was reproduced
tested the kernel from here today with the same result: https:= //kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc4/ generic amd64
I have updated to Ubuntu 19.04 and still getting the same resu= lt. Please let me know what steps to take next to get this issue resolved.
I would like to add to this some additional troubleshooting I = have performed, in case it is of use. just a short history: I am unable to suspend with any Linux distribution an= d be able to resume again. Currently running Ubuntu 19.04. I am attempting to follow the steps here to trace the problem: https://wiki.ubu= ntu.com/DebuggingKernelSuspend This is what I have done so far: $ sudo apt install pm-utils $ sudo sh -c "sync && echo 1 > /sys/power/pm_trace &&am= p; pm-suspend" I resumed but got my usual screen garbage (looks like static on the screen)= . I ssh'd in and did a sudo reboot Right away I ran this: $ dmesg > dmesg_post_boot.txt I looked for Magic number in the dmesg per the ubuntu wiki above and found these lines: [ 0.950964] Magic number: 0:66:1001 [ 0.950965] hash matches drivers/base/power/main.c:1012 Now the instructions are to exclude this module from the next boot and see = if I can replicate the problem. How do I exclude main.c or do I even want to? Is= it even possible that the bug is here?
Created atta=
chment 144270 [details]
Most Recent dmesg with magic number
I can reproduce on the same machine, but I get rainbow static,= not grey.
yes i should mention most of my static is grey but there are c= olours in there as well
I can confirm this behavior at Ubuntu 18.04.2 LTS with Acer PH= 517-61 notebook. The minor addition is that the issue concerns only the built-in display. In= two display configuration after wake up the external display seems to be normal= .
happened to me too using Opensuse Tumbleweed with kernel 5.1.7= and MESA 19.0.5, I have been try to disable power management in amdgpu via kernel paramater = but still happen. this happen to me while I play some game(s) such Mutant Zero Year and Uboat= on the STEAM, while other games seems doesnt trigger this static greyed display such as The Witcher 3 I cant log/reproduce any error messages since I'm using the laptop display (Acer Predator Helios 500 Ryzen 2700 with vega56) but maybe I can show my recorded video taken from my phone while this displ= ay glitch happened.
This issue also occurs on Windows. AMD support says that it wi= ll be fixed in the next Windows update; could they possibly contribute that same fix to Li= nux?
| What | Removed | Added |
|---|---|---|
| Resolution | --- | MOVED |
| Status | NEW | RESOLVED |
-- 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/726.