From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@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 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0313544602==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2E7296E57E for ; Tue, 26 Jun 2018 14:35:07 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0313544602== Content-Type: multipart/alternative; boundary="15300237070.f0268C1.17548" Content-Transfer-Encoding: 7bit --15300237070.f0268C1.17548 Date: Tue, 26 Jun 2018 14:35:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D107045 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=3D140343&action=3Dedit 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 activat= ion 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=3D1 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:=20 amdgpu: [powerplay]=20 failed to send message 62 ret is 0=20 amdgpu: [powerplay]=20 last message was failed ret is 0 amdgpu: [powerplay]=20 failed to send message 18f ret is 0=20 and then finally:=20 [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 af= ter 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" pha= se. Any ideas how to tackle that or extract some more usable error message from= my system? --=20 You are receiving this mail because: You are the assignee for the bug.= --15300237070.f0268C1.17548 Date: Tue, 26 Jun 2018 14:35:07 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
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 [details]
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=3D1 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:=20

  amdgpu: [powerplay]=20
           failed to send message 62 ret is 0=20
  amdgpu: [powerplay]=20
           last message was failed ret is 0
  amdgpu: [powerplay]=20
           failed to send message 18f ret is 0=20

and then finally:=20

  [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 af=
ter
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.
= --15300237070.f0268C1.17548-- --===============0313544602== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0313544602==--