Bug 105005 - No image after downtime (RX460)
Summary: No image after downtime (RX460)
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-07 19:29 UTC by Dmitry
Modified: 2018-03-18 19:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
photo (468.77 KB, image/jpeg)
2018-02-07 19:29 UTC, Dmitry
no flags Details
dmesg (71.00 KB, text/plain)
2018-02-07 21:48 UTC, Dmitry
no flags Details
Xorg log (63.19 KB, text/plain)
2018-02-07 21:50 UTC, Dmitry
no flags Details

Description Dmitry 2018-02-07 19:29:15 UTC
Created attachment 137221 [details]
photo

No display after idle for RX460 after upgrading to linux 4.15.1 distribution Arch. DC is not included, the problem on DP and HDMI. Also this problem even earlier, long ago, appeared on AMD Kaveri a10 7850k.

P.S. monitor AOC G2260VWQ6
Comment 1 Alex Deucher 2018-02-07 20:24:10 UTC
Please include your dmesg output and Xorg log if using X.
Comment 2 Alex Deucher 2018-02-07 20:24:32 UTC
Does it work with DC enabled?
Comment 3 Dmitry 2018-02-07 21:48:18 UTC
Created attachment 137222 [details]
dmesg

Attach dmesg
Comment 4 Dmitry 2018-02-07 21:50:49 UTC
Created attachment 137223 [details]
Xorg log

Attach Xorg log. DC then turned, I'll watch the reaction.
Comment 5 Dmitry 2018-02-08 06:11:17 UTC
dc1 + hdmi. The problem remained
Comment 6 Michel Dänzer 2018-02-08 09:29:55 UTC
Did you capture the Xorg log and dmesg before or after the problem occurred? If before, can you grab them again after?

What was the last kernel version where this didn't happen?
Comment 7 Dmitry 2018-02-08 12:05:21 UTC
After rebooting done due to this problem. Without the screen it is problematic to do, immediately after.

4.14.15-1
Comment 8 Michel Dänzer 2018-02-08 14:36:36 UTC
(In reply to Dmitry from comment #7)
> After rebooting done due to this problem. Without the screen it is
> problematic to do, immediately after.

If you have another computer, you can do it via ssh.


> 4.14.15-1

Any chance you can use git bisect to isolate the change between 4.14 and 4.15 which introduced the problem?
Comment 9 Dmitry 2018-02-09 19:11:05 UTC
I will not be able to do, not enough skill.

Tried to drag through TV files, TV breaks after the loss of the signal on the main machine. Also tried to register in the console dmesg creation with the switched-off screen, but nothing left. Perhaps there is a bug not with the video, and no signal from keyboard and mouse. Why not get out of standby.
Comment 10 Dmitry 2018-02-19 12:03:31 UTC
Now on 4.15.3 - 2 problems already there. The problem is not relevant.
Comment 11 Dmitry 2018-02-21 06:13:44 UTC
The kernel update didn't fix the problem, I thought. But now I know what the bug is about. This happens when you enable vertical sync in the settings of xfce.
Comment 12 Michel Dänzer 2018-02-21 08:52:58 UTC
Does this problem also happen using xf86-video-amdgpu instead of the modesetting driver with Xorg?
Comment 13 Dmitry 2018-02-23 08:24:17 UTC
In the case of option tearfree on came out of sleep. But there was a bug that flew in resolution 1366x768 and 1080p was not available. But it is possible problems xfce4, or I config the curve did. I have there

Section "Screen"
       Identifier     "Screen"
       DefaultDepth    24
       SubSection      "Display"
               Depth   24
       EndSubSection
EndSection

option tearfree on
Comment 14 Dmitry 2018-02-23 16:52:18 UTC
Because "tearfree true" is also not loaded Arch further, it literally immediately after removing the line. The problem is a bit similar.
Comment 15 Dmitry 2018-03-18 19:47:18 UTC
TearFree works, I did the configuration file wrong. Problems if the string is entered after "EndSection".

P.S. But with the inclusion of regular V-sync xorg, still problems even with the latest xf86-amgpu.


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.