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: Mon, 04 Feb 2019 03:17:14 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0157303412==" 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 3B2466E37C for ; Mon, 4 Feb 2019 03:17:15 +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 --===============0157303412== Content-Type: multipart/alternative; boundary="15492502352.FaFbed.309" Content-Transfer-Encoding: 7bit --15492502352.FaFbed.309 Date: Mon, 4 Feb 2019 03:17:15 +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 #65 from jake.hedges@yahoo.com --- Adding my PC to the pile affected by this - Ryzen 5 1600=20 Aorus RX 480 Debian (stretch)=20 2x8GB G.Skill DIMM (previously OC, but now everything in BIOS is "optimized default") ASUS ROG STRIX B350-F with latest bios/aegesa 4207 I am windows migrant who went cold turkey into Linux. Debian has been kind= to me minus a few hiccups and re-installs. My very first few installations ha= ve been the most stable sadly. Finally, I have pin pointed my issue to this thread.=20=20 /var/log/syslog demonstrates the GPU failure messages right before crash.=20 Issue seems to occur whether I have linux-firmware installed or not. Most recently, I had crash simply opening "show applications" in GNOME.=20=20 Crash is the same as others have stated. Screen blips and goes black. Fans spin up high speed. (I did not test ssh), but you cannot use reset button.= =20 The machine must be hard power down in order to recover. Twice now this has corrupted file system to the point where it would not boot normally. Since= , I was not versed enough to recover manually, I just re-installed.=20=20 As this is my first hard shot at Linux, this is quite a damper on what was a very exciting change. For now, I have applied the kernel params mentioned above and will report back should I crash again. --=20 You are receiving this mail because: You are the assignee for the bug.= --15492502352.FaFbed.309 Date: Mon, 4 Feb 2019 03:17:15 +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 # 65 on bug 10573= 3 from jake.hedges&= #64;yahoo.com
Adding my PC to the pile affected by this -

Ryzen 5 1600=20
Aorus RX 480
Debian (stretch)=20
2x8GB G.Skill DIMM (previously OC, but now everything in BIOS is "opti=
mized
default")
ASUS ROG STRIX B350-F with latest bios/aegesa 4207

I am windows migrant who went cold turkey into Linux.  Debian has been kind=
 to
me minus a few hiccups and re-installs.  My very first few installations ha=
ve
been the most stable sadly.  Finally, I have pin pointed my issue to this
thread.=20=20

/var/log/syslog demonstrates the GPU failure messages right before crash.=20
Issue seems to occur whether I have linux-firmware installed or not.  Most
recently, I had crash simply opening "show applications" in GNOME=
.=20=20

Crash is the same as others have stated.  Screen blips and goes black.  Fans
spin up high speed.  (I did not test ssh), but you cannot use reset button.=
=20
The machine must be hard power down in order to recover.  Twice now this has
corrupted file system to the point where it would not boot normally.  Since=
, I
was not versed enough to recover manually, I just re-installed.=20=20

As this is my first hard shot at Linux, this is quite a damper on what was a
very exciting change.  For now, I have applied the kernel params mentioned
above and will report back should I crash again.


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