All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106671] Frequent lock ups for AMD RX 550 graphics card
Date: Tue, 04 Sep 2018 19:27:43 +0000	[thread overview]
Message-ID: <bug-106671-502-4o9lJH1ZqA@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106671-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2647 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106671

--- Comment #9 from Alan W. Irwin <Alan.W.Irwin1234@gmail.com> ---
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.

[-- Attachment #1.2: Type: text/html, Size: 3432 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

  parent reply	other threads:[~2018-09-04 19:27 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
2018-09-04 19:26 ` bugzilla-daemon
2018-09-04 19:27 ` bugzilla-daemon [this message]
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-4o9lJH1ZqA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.