[Bug 106671] New: Frequent lock ups for AMD RX 550 graphics card

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat May 26 19:08:05 UTC 2018


            Bug ID: 106671
           Summary: Frequent lock ups for AMD RX 550 graphics card
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/AMDgpu
          Assignee: xorg-driver-ati at lists.x.org
          Reporter: Alan.W.Irwin1234 at gmail.com
        QA Contact: xorg-team at lists.x.org

This new computer has passed a fairly stringent non-graphics hardware test (an
rsync of 0.5TB of files followed by a second rsync using the --checksum
option which showed every bit was identical between the external drive source
and internal drive destination of the rsync) and also if I mostly (except
for the Linux console login prompt) bypass the RX 550 for display by running
applications on the new computer while displaying on my old computer's X
server, there are no lock ups so far in this mode.  So these are pretty strong
indications that the frequent (up to three times per day) lock ups I experience
when using the RX 550 for X graphical display are due to some bug in the amdgpu
X driver or its Linux kernel support.

I have also reported this issue at
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900087> which includes more
detail concerning software
versions, X logs, etc. for my Debian Buster versions of everything.

Of course, Debian Buster is likely a bit behind the cutting edge for both
kernel and X.  So to check if the latest kernel and X already solve the lock up
problems I am having with the Buster version I assume I will have to build both
kernel and X.  I do have general experience building Linux software but it has
been years since I built a Linux kernel and I have never built X before.  So
specific advice on how to build the Linux kernel and X and especially
integrating those built results into Debian Buster without messing up the
system would be most appreciated.

In the event that the latest kernel and X does not solve this issue, then I
would be ready to do any additional tests you might like to help you narrow
down what is the cause of these lock ups.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.x.org/archives/xorg-driver-ati/attachments/20180526/e5bb257f/attachment.html>

More information about the xorg-driver-ati mailing list