From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106671] Frequent lock ups for AMD RX 550 graphics card
Date: Wed, 29 Aug 2018 23:25:07 +0000 [thread overview]
Message-ID: <bug-106671-502-CtFojRYeOT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106671-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2210 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #7 from Alan W. Irwin <Alan.W.Irwin1234@gmail.com> ---
Please remove the resolution of this bug as FIXED.
The reason for this request is subsequent kernel-4.16.x use after the initial
success I reported continued to show lock ups whenever this graphics card was
used. Yesterday, I tried kernel-4.17.17-1 from Debian Buster (the first time I
had tried any kernel-4.17.x version) in great anticipation these kernel lockups
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 within a
half hour or so followed by one roughly 8 hours later. For what it is worth, 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 failing
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 Buster
firmware-amd-graphics package are not sufficient to stabilize use of this AMD
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 sale
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 record.
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.
[-- Attachment #1.2: Type: text/html, Size: 2995 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-29 23:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-106671-502@http.bugs.freedesktop.org/>
2018-05-28 8:47 ` [Bug 106671] Frequent lock ups for AMD RX 550 graphics card bugzilla-daemon
2018-05-28 18:07 ` bugzilla-daemon
2018-05-28 18:08 ` bugzilla-daemon
2018-05-28 18:32 ` bugzilla-daemon
2018-06-02 16:51 ` bugzilla-daemon
2018-06-02 16:54 ` bugzilla-daemon
2018-08-29 23:25 ` bugzilla-daemon [this message]
2018-09-04 19:26 ` bugzilla-daemon
2018-09-04 19:27 ` bugzilla-daemon
2018-09-05 7:37 ` bugzilla-daemon
2018-09-06 1:26 ` bugzilla-daemon
2018-09-06 6:56 ` bugzilla-daemon
2018-09-07 22:23 ` bugzilla-daemon
2018-09-07 22:36 ` bugzilla-daemon
2018-09-14 23:44 ` bugzilla-daemon
2018-09-15 0:04 ` bugzilla-daemon
2018-09-15 0:52 ` bugzilla-daemon
2018-09-24 4:44 ` bugzilla-daemon
2018-09-24 5:21 ` bugzilla-daemon
2018-09-24 5:34 ` bugzilla-daemon
2018-09-24 19:35 ` bugzilla-daemon
2018-09-24 19:58 ` bugzilla-daemon
2018-10-04 5:53 ` bugzilla-daemon
2018-10-05 1:39 ` bugzilla-daemon
2018-10-05 8:35 ` bugzilla-daemon
2018-10-05 8:40 ` bugzilla-daemon
2018-10-05 9:32 ` bugzilla-daemon
2018-10-05 9:59 ` bugzilla-daemon
2018-10-06 0:32 ` bugzilla-daemon
2018-10-17 21:28 ` bugzilla-daemon
2018-10-17 21:54 ` bugzilla-daemon
2018-10-21 5:58 ` bugzilla-daemon
2018-10-21 6:20 ` bugzilla-daemon
2018-11-04 5:56 ` bugzilla-daemon
2018-11-04 6:40 ` bugzilla-daemon
2018-11-10 8:38 ` bugzilla-daemon
2018-11-15 2:51 ` bugzilla-daemon
2019-09-25 18:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-106671-502-CtFojRYeOT@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).