From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 106671] Frequent lock ups for AMD RX 550 graphics card Date: Thu, 06 Sep 2018 01:26:14 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0895758928==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 6F9F46E462 for ; Thu, 6 Sep 2018 01:26:14 +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 --===============0895758928== Content-Type: multipart/alternative; boundary="15361971740.aCfbcabFf.24062" Content-Transfer-Encoding: 7bit --15361971740.aCfbcabFf.24062 Date: Thu, 6 Sep 2018 01:26:14 +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=3D106671 --- Comment #11 from Alan W. Irwin --- Thanks for that idle=3Dnomwait suggestion which I have now just tried (veri= fied by irwin@merlin> cat /proc/cmdline BOOT_IMAGE=3D/boot/vmlinuz-4.17.0-3-amd64 root=3DUUID=3D1e45a1ee-a5d6-4327-9a7b-2663ffc0b157 ro rootwait quiet idle= =3Dnomwait ) and I now indeed have a stable result. However, that is currently just f= or the last 5 minutes in remote access mode. :-) So we will see how this goes for, say, the next two weeks, to see if I can beat my last 4.17.17 remote access uptime record of 6 days. With regard to your MB BIOS update suggestion, I am going to hold back on t= hat for a while since the techs from a local computer company that assembled my= box in May felt such updates were dangerous and therefore a last resort. And t= hat is also the consistent advice I have gotten for the other 3 Linux boxes I h= ave had assembled for me since I started using Linux in 1996. Of course, this = year may be a special case with all the Meltdown (although not for this AMD hardware) and many variants of SPECTRE out there so I do plan to update the BIOS within the next couple of months on the assumption that the SPECTRE BI= OS mitigations recommended by AMD to ASUS for this hardware (PRIME B350+ MB wi= th AMD Ryzen 7 1700 CPU, 64GB RAM, and ASUS RX 550 graphics card) will have matured by then.=20=20 But before I implement that planned BIOS update, I am hoping that the curre= nt cutting-edge Linux graphics stack (which according to a senior Phoronix pos= ter works well for the RX 560) will also give me stable direct-display results = for the RX 550 once that version of the graphics stack propagates to Debian Testing. I estimate that propagation time will be a couple of more months based on how quickly elements of the cutting-edge Linux graphics stack such= as the kernel has propagated in the past from upstream to Debian Testing. In sum, it is a waiting game now to see if your idle=3Dnomwait suggestion restores the complete Linux stability I was used to with my old box (for De= bian Oldstable =3D Jessie) for at least the remote display case, and if that sta= bility is obviously much better (i.e., at least a couple of weeks uptime with no lockups) then I will try the direct display case again with idle=3Dnomwait = to see if it makes that case stable as well. Thanks, Michel, for your on-going helpful suggestions for dealing with this troubling instability issue (these troubling instability issues?) for my new Linux box. Alan --=20 You are receiving this mail because: You are the assignee for the bug.= --15361971740.aCfbcabFf.24062 Date: Thu, 6 Sep 2018 01:26:14 +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 # 11 on bug 10667= 1 from Alan W. Irwin 
Thanks for that idle=3Dnomwait suggestion which I have now jus=
t tried (verified
by

irwin@merlin> cat /proc/cmdline
BOOT_IMAGE=3D/boot/vmlinuz-4.17.0-3-amd64
root=3DUUID=3D1e45a1ee-a5d6-4327-9a7b-2663ffc0b157 ro rootwait quiet idle=
=3Dnomwait

) and I now indeed have a stable result.  However, that is currently just f=
or
the last 5 minutes in remote access mode.  :-)  So we will see how this goes
for, say, the next two weeks, to see if I can beat my last 4.17.17 remote
access uptime record of 6 days.

With regard to your MB BIOS update suggestion, I am going to hold back on t=
hat
for a while since the techs from a local computer company that assembled my=
 box
in May felt such updates were dangerous and therefore a last resort.  And t=
hat
is also the consistent advice I have gotten for the other 3 Linux boxes I h=
ave
had assembled for me since I started using Linux in 1996.  Of course, this =
year
may be a special case with all the Meltdown (although not for this AMD
hardware) and many variants of SPECTRE out there so I do plan to update the
BIOS within the next couple of months on the assumption that the SPECTRE BI=
OS
mitigations recommended by AMD to ASUS for this hardware (PRIME B350+ MB wi=
th
AMD Ryzen 7 1700 CPU, 64GB RAM, and ASUS RX 550 graphics card) will have
matured by then.=20=20

But before I implement that planned BIOS update, I am hoping that the curre=
nt
cutting-edge Linux graphics stack (which according to a senior Phoronix pos=
ter
works well for the RX 560) will also give me stable direct-display results =
for
the RX 550 once that version of the graphics stack propagates to Debian
Testing.  I estimate that propagation time will be a couple of more months
based on how quickly elements of the cutting-edge Linux graphics stack such=
 as
the kernel has propagated in the past from upstream to Debian Testing.

In sum, it is a waiting game now to see if your idle=3Dnomwait suggestion
restores the complete Linux stability I was used to with my old box (for De=
bian
Oldstable =3D Jessie) for at least the remote display case, and if that sta=
bility
is obviously much better (i.e., at least a couple of weeks uptime with no
lockups) then I will try the direct display case again with idle=3Dnomwait =
to see
if it makes that case stable as well.

Thanks, Michel, for your on-going helpful suggestions for dealing with this
troubling instability issue (these troubling instability issues?) for my new
Linux box.

Alan

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