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: Tue, 26 Jun 2018 14:35:06 +0000 [thread overview]
Message-ID: <bug-107045-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2305 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107045
Bug ID: 107045
Summary: [4.18rc2] RX470 dGPU on hybrid laptop freezes screen
after use
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: taijian@posteo.de
Created attachment 140343
--> https://bugs.freedesktop.org/attachment.cgi?id=140343&action=edit
full dmesg output via 'journalctl -kb -1'
With kernel 4.18rc dpm on my hybrid laptop is finally working (thanks again to
everyone who helped out getting it this far - see bug #104064, bug #106597 and
bug #105760). However, it is still not actually usable, because any activation
of the dGPU leads to a system freeze shortly thereafter. It does not really
matter HOW the dGPU is triggered - be it running a graphical application via
DRI_PRIME=1 or just querying #lshw. The dGPU activates and then tries to power
down again, but that seems to be problematic as the (graphical) system will
invariable freeze and become unresponsive.
The best I have been able to reconstruct from the journal is that whenever the
dGPU is called, it will first do this:
[drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
followed by a bunch of this:
amdgpu: [powerplay]
failed to send message 62 ret is 0
amdgpu: [powerplay]
last message was failed ret is 0
amdgpu: [powerplay]
failed to send message 18f ret is 0
and then finally:
[drm] UVD and UVD ENC initialized successfully.
[drm] VCE initialized successfully.
[drm] Cannot find any crtc or sizes
amdgpu 0000:01:00.0: GPU pci config reset
Sometimes, this will work more than once, sometimes the first invocation after
boot will crash. This seems to be somewhat random. However, the crash will
always come in the "[powerplay] ...failed to send message 18f ret is 0" phase.
Any ideas how to tackle that or extract some more usable error message from my
system?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4508 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 reply other threads:[~2018-06-26 14:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 14:35 bugzilla-daemon [this message]
2018-06-26 14:37 ` [Bug 107045] [4.18rc2] RX470 dGPU on hybrid laptop freezes screen after use 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
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@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.