<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c22">Comment # 22</a> on <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">bug 106671</a> from <a class="email" href="mailto:Alan.W.Irwin1234@gmail.com" title="Alan W. Irwin <Alan.W.Irwin1234@gmail.com>"> Alan W. Irwin</a> <pre>This last stability test lasted only 17.5 hours before the lockup. See the latest attached tarball for the relevant log files (which capture everything during this short up time) and dmesg output. As far as I can tell there is nothing in those log files relevant to the lockup, e.g., no burst of null ascii characters like what occurred in the log files for the previous experiment. There are some segfaults associated with a cron task I have configured every morning starting at 4:32, but those always occur for that task (which is a complete build and test of CMake) so I don't think they are relevant. The actual lockup today happened with one inactive desktop running on the X-terminal and one active desktop running on the new box. (I was editing a file with Emacs.) Also, the symptoms of this lockup were more severe, i.e., ping did not work from the X-terminal to the new box. But as always there was no way to shut down the new box properly so I had to do that with the reset button. Since I bought the new box in May remote access from an X-terminal has only locked up twice (one of those detailed here), and after a relatively long period of time. So tests where the X-terminal use is the only way to access the new box seems in general much more stable than direct use (as in the present case with such a short time before the lockup). And I haven't tried sole use of the X-terminal for a while now, and that may be completely stable with the new kernel. So my conclusion remains that the problem is associated with the Debian Buster graphics stack (and likely also the very latest graphics stack if someone will do some up time tests for modern AMD graphics cards for that stack) used to display and control the RX 550 card on the new box. I have now started a new test (as of 9:08:19 today) with all graphics stack versions and kernel parameters the same as for the previous test in hopes that when the inevitable lockup comes the log files will be more informative. Please let me know if you have some other experiment you would like me to try.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>