All of lore.kernel.org
 help / color / mirror / Atom feed
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, 31 Aug 2018 19:21:15 +0000	[thread overview]
Message-ID: <bug-107045-502-EYmG0y1LHE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107045-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 4750 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107045

--- Comment #22 from taijian@posteo.de ---
OK, after some further testing, here is some more information on my issue:

1) It turns out that the crashing/hanging behaviour ONLY happens when I'm
logged into a graphical session (GNOME in my case). When working exclusively
from a tty, then the system remains stable.

2) A Wayland session seems to be slightly more stable/resillient to crashing
than an X11 session. While the latter crashes almost immediately when doing
anything with the backlight, the former goes through a couple of cycles of
extreme lag, stuttering and recovery before finally succumbing to whatever the
problem is.

3) I can reliably and reproduceably crash my graphical session by messing with
screen brightness in any way - either through the tools of the graphical shell
or by doing #echo X > /sys/class/backlight/intel_backlight/brightness.

4) Why is this an amdgpu bug then? Because the issue only arises when amdgpu is
loaded in DC mode, because in this mode the display connectors directly
connected to the dGPU (DP, eDP and HDMI) are being ennumerated. With dc=0 they
are not recognized and can therefore not create any problems.

5) What I think happens is that the graphical shell tries to adjust brightness
on the displays that are ennumerated as connectors but not actually connected,
and by doing so eventually get amdgpu to crash irrecoverably. 

6) When intel_backlight gets manipulated, the following always shows up in
dmesg (the first couple of times the dGPU gets to the 'reset', at some point is
just crashes before that, taking the system with it).


Aug 31 17:58:54 alien-arch kernel: [drm] PCIE GART of 256M enabled (table at
0x000000F400000000).
Aug 31 17:58:54 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 62 ret is 0 
Aug 31 17:58:54 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:58:55 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 18f ret is 0 
Aug 31 17:58:55 alien-arch kernel: [drm] UVD and UVD ENC initialized
successfully.
Aug 31 17:58:55 alien-arch kernel: [drm] VCE initialized successfully.
Aug 31 17:58:56 alien-arch kernel: [drm] Cannot find any crtc or sizes
Aug 31 17:58:57 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 15b ret is 0 
Aug 31 17:58:58 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 155 ret is 0 
Aug 31 17:59:06 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 281 ret is 0 
Aug 31 17:59:07 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:59:07 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 261 ret is 0 
Aug 31 17:59:08 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:59:08 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 261 ret is 0 
Aug 31 17:59:09 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:59:10 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 261 ret is 0 
Aug 31 17:59:10 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:59:11 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 261 ret is 0 
Aug 31 17:59:12 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:59:12 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 261 ret is 0 
Aug 31 17:59:13 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:59:13 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 261 ret is 0 
Aug 31 17:59:14 alien-arch kernel: amdgpu: [powerplay] 
                                    last message was failed ret is 0
Aug 31 17:59:14 alien-arch kernel: amdgpu: [powerplay] 
                                    failed to send message 261 ret is 0 
Aug 31 17:59:14 alien-arch kernel: amdgpu 0000:01:00.0: GPU pci config reset

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 5539 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

  parent reply	other threads:[~2018-08-31 19:21 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 [this message]
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-EYmG0y1LHE@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.