From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105733] Amdgpu randomly hangs and only ssh works. Mouse cursor moves sometimes but does nothing. Keyboard stops working. Date: Thu, 17 Jan 2019 22:32:08 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1334818480==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id B730D6F5A0 for ; Thu, 17 Jan 2019 22:32:08 +0000 (UTC) In-Reply-To: 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 --===============1334818480== Content-Type: multipart/alternative; boundary="15477643284.ed7a4b.26377" Content-Transfer-Encoding: 7bit --15477643284.ed7a4b.26377 Date: Thu, 17 Jan 2019 22:32:08 +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=3D105733 --- Comment #56 from las@protonmail.ch --- Also, forgot to mention, but the new GPU recovery thing doesn't work, and it would make the following error in dmesg: jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=3D2792, emitted seq=3D2795 jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Proc= ess information: process pid 0 thread pid 0 jan 16 16:43:26 las kernel: amdgpu 0000:08:00.0: GPU reset begin! jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring= gfx timeout, signaled seq=3D7013, emitted seq=3D7015 jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Proc= ess information: process sway pid 1328 thread sway:cs0 pid 1329 jan 16 16:43:26 las kernel: amdgpu 0000:08:00.0: GPU reset begin! jan 16 16:43:26 las kernel: amdgpu: [powerplay]=20 failed to send message 261 ret is 0=20 jan 16 16:43:27 las kernel: amdgpu: [powerplay]=20 last message was failed ret is 0 jan 16 16:43:28 las kernel: amdgpu: [powerplay]=20 failed to send message 261 ret is 0=20 lines 955-1010/1010 (END) (Fetched through `journalctl -ekb`) This however stopped once I switched to DVI-D, since I now get no errors at all. --=20 You are receiving this mail because: You are the assignee for the bug.= --15477643284.ed7a4b.26377 Date: Thu, 17 Jan 2019 22:32:08 +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

Comme= nt # 56 on bug 10573= 3 from las@protonmail.c= h 
Also, forgot to mention, but the new GPU recovery thing doesn'=
t work, and it
would make the following error in dmesg:

jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
sdma0 timeout, signaled seq=3D2792, emitted seq=3D2795
jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Proc=
ess
information: process  pid 0 thread  pid 0
jan 16 16:43:26 las kernel: amdgpu 0000:08:00.0: GPU reset begin!
jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring=
 gfx
timeout, signaled seq=3D7013, emitted seq=3D7015
jan 16 16:43:26 las kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Proc=
ess
information: process sway pid 1328 thread sway:cs0 pid 1329
jan 16 16:43:26 las kernel: amdgpu 0000:08:00.0: GPU reset begin!
jan 16 16:43:26 las kernel: amdgpu: [powerplay]=20
                             failed to send message 261 ret is 0=20
jan 16 16:43:27 las kernel: amdgpu: [powerplay]=20
                             last message was failed ret is 0
jan 16 16:43:28 las kernel: amdgpu: [powerplay]=20
                             failed to send message 261 ret is 0=20
lines 955-1010/1010 (END)

(Fetched through `journalctl -ekb<boot ID>`)

This however stopped once I switched to DVI-D, since I now get no errors at
all.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15477643284.ed7a4b.26377-- --===============1334818480== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1334818480==--