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: Fri, 25 Jan 2019 07:36:40 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1142214183==" 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 130756F27E for ; Fri, 25 Jan 2019 07:36:40 +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 --===============1142214183== Content-Type: multipart/alternative; boundary="15484018000.C8af1.22788" Content-Transfer-Encoding: 7bit --15484018000.C8af1.22788 Date: Fri, 25 Jan 2019 07:36:40 +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 #61 from Zheng Luo --- I experienced similar problems, but mine is much worse. I can't recover from black screen after reboot/hard reset unless I drain the builtin battery. However this problem disappears in 5.0rc3 (in contrast to the buggy 4.20). Strongly suspect there are some kinds of firmware corruption --=20 You are receiving this mail because: You are the assignee for the bug.= --15484018000.C8af1.22788 Date: Fri, 25 Jan 2019 07:36:40 +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 # 61 on bug 10573= 3 from = Zheng Luo 
I experienced similar problems, but mine is much worse. I can'=
t recover from
black screen after reboot/hard reset unless I drain the builtin battery.
However this problem disappears in 5.0rc3 (in contrast to the buggy 4.20).
Strongly suspect there are some kinds of firmware corruption

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