From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201015] [amdgpu] BUG: unable to handle kernel NULL pointer dereference on resume with 2 monitors (vega)
Date: Mon, 10 Sep 2018 18:46:34 +0000 [thread overview]
Message-ID: <bug-201015-2300-SCuQyyDtma@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201015-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201015
--- Comment #6 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) ---
I'd imagine you're probably running GNOME on Wayland from that setup
environment.
The patch seems to fix the null pointer deference but you're probably getting a
black screen from those failed atomic commits.
Might not be a problem with the driver but with the GNOME Wayland
implementation - I would need to do more investigation to see which atomic
commits are failing and if the failures are valid (but unchecked).
You would probably not see this occur for GNOME over Xorg.
--
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
next prev parent reply other threads:[~2018-09-10 18:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 6:06 [Bug 201015] New: [amdgpu] BUG: unable to handle kernel NULL pointer dereference on resume with 2 monitors (vega) bugzilla-daemon
2018-09-05 6:08 ` [Bug 201015] " bugzilla-daemon
2018-09-05 7:40 ` bugzilla-daemon
2018-09-05 9:37 ` bugzilla-daemon
2018-09-10 17:55 ` bugzilla-daemon
2018-09-10 18:34 ` bugzilla-daemon
2018-09-10 18:46 ` bugzilla-daemon [this message]
2018-09-10 20:34 ` bugzilla-daemon
2018-09-11 19:16 ` bugzilla-daemon
2018-09-11 19:19 ` bugzilla-daemon
2018-10-03 16:17 ` bugzilla-daemon
2018-11-10 2:08 ` 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-201015-2300-SCuQyyDtma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox