All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202217] Integrated laptop display doesnt come back up after using PRIME on wayland
Date: Fri, 11 Jan 2019 10:40:43 +0000	[thread overview]
Message-ID: <bug-202217-2300-WNMjfXkovm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202217-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202217

--- Comment #3 from Haxk20 (haxk612@gmail.com) ---
(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.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-01-11 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 20:07 [Bug 202217] New: Integrated laptop display doesnt come back up after using PRIME on wayland bugzilla-daemon
2019-01-10 20:08 ` [Bug 202217] " bugzilla-daemon
2019-01-10 20:41 ` bugzilla-daemon
2019-01-11 10:40 ` bugzilla-daemon [this message]
2019-01-11 20:43 ` bugzilla-daemon
2019-01-12  9:55 ` bugzilla-daemon
2019-01-12  9:56 ` bugzilla-daemon
2019-01-15 15:05 ` bugzilla-daemon
2019-01-15 19:01 ` bugzilla-daemon
2019-01-18 14:16 ` 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-202217-2300-WNMjfXkovm@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.