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: Wed, 29 Aug 2018 23:25:07 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1774426923==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2CEE86E660 for ; Wed, 29 Aug 2018 23:25:07 +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 --===============1774426923== Content-Type: multipart/alternative; boundary="15355851071.68A7aC8.6883" Content-Transfer-Encoding: 7bit --15355851071.68A7aC8.6883 Date: Wed, 29 Aug 2018 23:25: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=3D106671 --- Comment #7 from Alan W. Irwin --- Please remove the resolution of this bug as FIXED. The reason for this request is subsequent kernel-4.16.x use after the initi= al success I reported continued to show lock ups whenever this graphics card w= as used. Yesterday, I tried kernel-4.17.17-1 from Debian Buster (the first ti= me I had tried any kernel-4.17.x version) in great anticipation these kernel loc= kups would be fixed (since kernel-4.17.x apparently contains lots of AMD graphics fixes). But when I used this graphics card for ordinary direct desktop use= (as opposed to accessing my desktop on the new computer via an X-terminal which= is so far the only stable way I can use my new computer), I got a lockup withi= n a half hour or so followed by one roughly 8 hours later. For what it is wort= h, I have also installed mesa-8.1.6-1 and version 20180518-1 of the firmware-amd-graphics package from Debian Buster before performing this fai= ling experiment. So it appears the substantial number of AMD graphics fixes in kernel-4.17.x= and mesa-18.1.y and installation of the relatively recent (from May) Debian Bus= ter firmware-amd-graphics package are not sufficient to stabilize use of this A= MD RX 550 graphics card. That is a big disappointment since this card should = no longer be considered cutting-edge hardware (i.e. it was first offered for s= ale at least 16 months ago) and this delay in fixing it cannot be attributed to non-cooperation from AMD since they appear to have a good open-source recor= d. Because of these on-going issues with direct use of this card, I am going back to using the X-terminal method with this kernel which experience with kernel-4.16.x shows is much more stable since it avoids using this graphics card completely (except for the direct display of the Linux console login prompt). I plan to again try the experiment of attempting to use this card directly = when kernel-4.18.x is promoted to Buster. But meanwhile, if you have any other suggestions I could try, please let me know. --=20 You are receiving this mail because: You are the assignee for the bug.= --15355851071.68A7aC8.6883 Date: Wed, 29 Aug 2018 23:25: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

Commen= t # 7 on bug 10667= 1 from Alan W. Irwin 
Please remove the resolution of this bug as FIXED.

The reason for this request is subsequent kernel-4.16.x use after the initi=
al
success I reported continued to show lock ups whenever this graphics card w=
as
used.  Yesterday, I tried kernel-4.17.17-1 from Debian Buster (the first ti=
me I
had tried any kernel-4.17.x version) in great anticipation these kernel loc=
kups
would be fixed (since kernel-4.17.x apparently contains lots of AMD graphics
fixes).  But when I used this graphics card for ordinary direct desktop use=
 (as
opposed to accessing my desktop on the new computer via an X-terminal which=
 is
so far the only stable way I can use my new computer), I got a lockup withi=
n a
half hour or so followed by one roughly 8 hours later.  For what it is wort=
h, I
have also installed mesa-8.1.6-1 and version 20180518-1 of the
firmware-amd-graphics package from Debian Buster before performing this fai=
ling
experiment.

So it appears the substantial number of AMD graphics fixes in kernel-4.17.x=
 and
mesa-18.1.y and installation of the relatively recent (from May) Debian Bus=
ter
firmware-amd-graphics package are not sufficient to stabilize use of this A=
MD
RX 550 graphics card.  That is a big disappointment since this card should =
no
longer be considered cutting-edge hardware (i.e. it was first offered for s=
ale
at least 16 months ago) and this delay in fixing it cannot be attributed to
non-cooperation from AMD since they appear to have a good open-source recor=
d.

Because of these on-going issues with direct use of this card, I am
going back to using the X-terminal method with this kernel which
experience with kernel-4.16.x shows is much more stable since it
avoids using this graphics card completely (except for the direct
display of the Linux console login prompt).

I plan to again try the experiment of attempting to use this card directly =
when
kernel-4.18.x is promoted to Buster.  But meanwhile, if you have any other
suggestions I could try, please let me know.

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