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: Wed, 17 Oct 2018 21:54:37 +0000	[thread overview]
Message-ID: <bug-106671-502-gqUpUXy8tu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106671-502@http.bugs.freedesktop.org/>


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

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

--- Comment #30 from Alan W. Irwin <Alan.W.Irwin1234@gmail.com> ---
This time the system lasted almost 14 days before the lockup.  See the latest
attachment for the log details which contain NMI messages followed by a burst
of ascii null characters (which in my experience can be due to different
threads or processes trying to write to the same file, i.e., the NMI error
messages themselves might have exposed another kernel bug).  Unlike the last
case of NMI mesages where an Intel network card was mentioned, the only
hardware I can see
mentioned in these messages is a particular cpu and my motherboard, e.g.,
Oct 17 13:25:02 merlin kernel: [1177237.021995] NMI watchdog: Watchdog detected
hard LOCKUP on cpu 13
[...]
Oct 17 13:25:02 merlin kernel: [1177237.022042] Hardware name: System
manufacturer System Product Name/PRIME B350-PLUS, BIOS 3803 01/22/2018

So this appears not to be hard evidence of a graphics stack bug since likely
any linux system component bug could lock up a cpu, but I am still pretty sure
this is a graphics stack issue with the RX 550 because of my prior evidence
showing
much better kernel stability if I do not use that RX550 card at all.

I started a new up-time experiment using today's snapshot of Debian Buster
which left most of the graphics stack the same other than libdrm-amdgpu1 which
has been updated from 2.4.94-1 to 2.4.95-1 and the 
linux kernel which has been updated from 4.18.6-1 to 4.18.10-2.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2388 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-10-17 21:54 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
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 [this message]
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-gqUpUXy8tu@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.