Comment # 9
on bug 106671
from Alan W. Irwin
We (there are two of us using this machine) just got yet another kernel lockup (no remote access possible with ssh, direct keyboard not working), but this is a case when we were remotely accessing this box with an X-terminal. In other words, the only use of the RX 550 was to display the command-line login prompt for the Linux console of the directly attached monitor until the lockup where it displayed the following message (roughly 15 times in the half-hour before I got out of the lockup by pushing the reset button.) watchdog: BUG: soft lockup - CPU#12 stuck for 22s! [firefox-esr:29266] (At the time we were both browsing different sites with firefox with one of those firefox instances running a couple of days, and as a security measure we both restrict the use of _javascript_ with the noscript extension to firefox.) I have attached a tarball containing log files (kern.log and syslog) that contain the lockup information (including the above message) as well as information about the fresh boot afterwards. (For what it is worth, that tarball also includes dmesg output which appears to contain information only about the fresh boot.) For this minimal use case for the RX 550, the Linux kernel lasted 6 days before the lockup which is much better than the direct use case where the lockups can occur as soon as a half hour after a fresh boot. So the current lockup could be due to an entirely different bug than in the lockups I have encountered for the direct use case. But, of course, minimal use is not zero use so currently I ascribe both the present remote-use lockup and the previous direct-use lockups to some incompatibility between the RX 550 and the Debian Testing graphics stack. That stack currently includes the following component versions: linux-image-4.17.0-3-amd64 4.17.17-1 firmware-amd-graphics 20180518-1 libdrm-amdgpu1:amd64 2.4.93-1 libglapi-mesa:amd64 18.1.6-1 xserver-xorg-video-amdgpu 18.0.1-1+b1 Please let me know if there are any other data you need or any experiments you would like me to try. In any case I plan to continue with remote use of this box while reporting lockup incidents as they occur. But I also plan to try direct use again whenever one of the components of the above stack gets significantly upgraded for Debian Testing.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
