Bug 202217 - Integrated laptop display doesnt come back up after using PRIME on wayland
Summary: Integrated laptop display doesnt come back up after using PRIME on wayland
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: All Linux
: P1 high
Assignee: drivers_video-dri
URL:
Keywords:
: 202197 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-01-10 20:07 UTC by Haxk20
Modified: 2019-01-18 14:16 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.0-rc1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (81.80 KB, text/plain)
2019-01-12 09:55 UTC, Haxk20
Details

Description Haxk20 2019-01-10 20:07:14 UTC
This issue was happening also on amd-staging-drm-next before 5.0rc1.

The issue is when GNOME with wayland is launched. Screen goes black after few seconds and doesnt come back up.

Expected result: Black screen and display coming back up as on older kernel versions
Actual result: Black screen and display not coming back up.

Black screen and display coming up is normal behavior when switching from iGPU to dGPU or vice versa.

This isnt an issue on Xorg because when switching from iGPU to dGPU because on Xorg display never goes black when switching.

Only way to use 5.0rc1 is to use Xorg which isnt a problem but i would like to run Wayland.

Laptop: Acer nitro 5
iGPU: VEGA 8
dGPU RX560X

If you need to run anything in terminal or get logs im happy to provide them.
*/This issue was originally posted in video-other but i realized that that is a wrong category/*
Comment 1 Haxk20 2019-01-10 20:08:16 UTC
*** Bug 202197 has been marked as a duplicate of this bug. ***
Comment 2 Alex Deucher 2019-01-10 20:41:44 UTC
Please attach your xorg log and dmesg output.  Can you provide more details on what exactly the issue is?  On hybrid laptops, the dGPU is used for rendering offload.  The local display is generally only attached to the APU.  If this is a regression, can you bisect?
Comment 3 Haxk20 2019-01-11 10:40:43 UTC
(In reply to Alex Deucher from comment #2)
> Please attach your xorg log and dmesg output.  Can you provide more details
> on what exactly the issue is?  On hybrid laptops, the dGPU is used for
> rendering offload.  The local display is generally only attached to the APU.
> If this is a regression, can you bisect?

The issue is that on Wayland when i use DRI_PRIME=1 to use dGPU for offloading the screen goes black and never comes back on. On 4.20 the screen would go black but would come back on after a second or two.

Will post logs later today.
And if i may ask whats the point of Xorg logs since this issue occurs ONLY in Wayland ?
On Xorg the screen works perfectly fine and actually when using DRI_PRIME=1 the display doesnt even go black for a sec.
The main issue with this bug is that when i turn on Wayland session of GNOME the display would show my desktop but after few seconds it would go black and then come back up. On 5.0 the screen goes black but never comes back up.
This makes it impossible to use Wayland session of GNOME.
Comment 4 Alex Deucher 2019-01-11 20:43:25 UTC
Don't worry about the xorg log.  Sorry, habit.
Comment 5 Haxk20 2019-01-12 09:55:51 UTC
Created attachment 280433 [details]
dmesg

Dmesg output right after screen went black.
Switched to tty3 and blindly took the dmesg.
Comment 6 Haxk20 2019-01-12 09:56:50 UTC
(In reply to Alex Deucher from comment #4)
> Don't worry about the xorg log.  Sorry, habit.

And what i noticed is that when the screen goes black then even after switching to ttyX the screen still stays black.
Comment 7 Haxk20 2019-01-15 15:05:17 UTC
I did some further testing. The bug seems to be that even when i run just TTY session without GNOME even launched and i suspend the laptop to turn off the screen then the screen doesnt come back up. But i can still type on keyboard and the machine does what i type. So i have to turn it off blindly.
This makes the machine unusable outside where you have to suspend the machine.
Comment 8 Haxk20 2019-01-18 14:16:11 UTC
Issue fixed as of the latest drm patches sent to kernel that will become RC3

Note You need to log in before you can comment on or make changes to this bug.