<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Frequent lock ups for AMD RX 550 graphics card"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106671">106671</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Frequent lock ups for AMD RX 550 graphics card
</td>
</tr>
<tr>
<th>Product</th>
<td>xorg
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver/AMDgpu
</td>
</tr>
<tr>
<th>Assignee</th>
<td>xorg-driver-ati@lists.x.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>Alan.W.Irwin1234@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>xorg-team@lists.x.org
</td>
</tr></table>
<p>
<div>
<pre>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
<<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900087">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900087</a>> 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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>