dri-devel.lists.freedesktop.org archive mirror
 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: Mon, 24 Sep 2018 19:58:45 +0000	[thread overview]
Message-ID: <bug-106671-502-dPhigxtWxN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106671-502@http.bugs.freedesktop.org/>


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

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

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

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

[-- Attachment #1.2: Type: text/html, Size: 3090 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-24 19:58 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 [this message]
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-dPhigxtWxN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).