From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107045] [4.18rc2] RX470 dGPU on hybrid laptop freezes screen after use
Date: Wed, 05 Sep 2018 21:46:16 +0000 [thread overview]
Message-ID: <bug-107045-502-VLKVQo6Hnv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107045-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 735 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107045
--- Comment #24 from taijian@posteo.de ---
OK, another update after another test, this time booting into a live system
without any graphical shell/login manager.
Here, manipulating /sys/class/intel_backlight/brightness does nothing to the
dGPU, so that part is clearly a user space bug.
However, a simple #lspci DOES crash the system in the manner described above,
so that part is still on amdgpu (and likely the root cause of the behaviour
described in my OP). Again, this is only an issue with dc=1 and not with dc=0.
Possibly related: https://bugzilla.kernel.org/show_bug.cgi?id=156341
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1586 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
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-05 21:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 14:35 [Bug 107045] [4.18rc2] RX470 dGPU on hybrid laptop freezes screen after use bugzilla-daemon
2018-06-26 14:37 ` bugzilla-daemon
2018-06-26 14:49 ` bugzilla-daemon
2018-06-26 16:13 ` bugzilla-daemon
2018-06-26 16:21 ` bugzilla-daemon
2018-06-26 21:30 ` bugzilla-daemon
2018-06-27 12:59 ` bugzilla-daemon
2018-06-27 14:17 ` bugzilla-daemon
2018-06-28 7:24 ` bugzilla-daemon
2018-06-29 8:37 ` bugzilla-daemon
2018-06-29 8:44 ` bugzilla-daemon
2018-06-29 8:56 ` bugzilla-daemon
2018-06-29 15:10 ` bugzilla-daemon
2018-06-29 16:04 ` bugzilla-daemon
2018-06-29 22:13 ` bugzilla-daemon
2018-07-20 15:13 ` bugzilla-daemon
2018-07-20 15:14 ` bugzilla-daemon
2018-07-20 16:35 ` bugzilla-daemon
2018-08-15 22:21 ` bugzilla-daemon
2018-08-16 7:05 ` bugzilla-daemon
2018-08-24 20:48 ` bugzilla-daemon
2018-08-28 16:48 ` bugzilla-daemon
2018-08-28 22:14 ` bugzilla-daemon
2018-08-31 19:21 ` bugzilla-daemon
2018-08-31 19:21 ` bugzilla-daemon
2018-09-05 21:46 ` bugzilla-daemon [this message]
2018-10-06 19:49 ` bugzilla-daemon
2018-10-06 19:50 ` 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-107045-502-VLKVQo6Hnv@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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;
as well as URLs for NNTP newsgroup(s).