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: Fri, 20 Jul 2018 15:13:49 +0000 [thread overview]
Message-ID: <bug-107045-502-foDKSZ5qVA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107045-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 892 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107045
--- Comment #15 from taijian@posteo.de ---
Created attachment 140733
--> https://bugs.freedesktop.org/attachment.cgi?id=140733&action=edit
dmesg output 4.18rc5 + drm-fixes-2018-07-20
OK, so I have some new, probably interesting dmesg output with the latest
mainline build.
What's happening here is that the system boots up, then my background display
brightness service goes to work (see here: https://github.com/FedeDP/Clight and
here: https://github.com/FedeDP/Clightd) and tries to adjust screen brightness.
This leads to a number of
RIP: 0010:dm_dp_aux_transfer+0xa5/0xb0 [amdgpu]
trace calls and then the system freeezes completely. And I mean completely, as
in not even sysrq + REISUB does anything. Does this help in any way?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1951 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-07-20 15:13 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 [this message]
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
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-foDKSZ5qVA@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 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.