From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106671] Frequent lock ups for AMD RX 550 graphics card
Date: Sat, 15 Sep 2018 00:04:12 +0000 [thread overview]
Message-ID: <bug-106671-502-wTIzwdbQOK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106671-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1501 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #16 from Alan W. Irwin <Alan.W.Irwin1234@gmail.com> ---
I was beginning to have some hope that the latest direct access experiment
would prove to be stable. However, just now it locked up again after almost 7
days. So the stability is substantially improved compared to before, and my
guess is that improvement is due to installation of the amd64-microcode package
from Debian Buster for this latest experiment.
However, this is still disappointing stability because typically for truly
stable systems I achieve up times of 30 days or longer with the only limit on
uptime being how often I have to reboot due to kernel upgrades.
I have attached a crash report tarball containing dmesg output as well as
various log files that captured all log activity before the lockup and the boot
afterward. I don't see anything concerning the crash in those log files, but I
may be missing something since I am no expert so I would appreciate it if you
took a look.
I have restarted exactly the same direct graphics access test again (with same
versions of graphics stack packages and your recommended idle=nomwait kernel
parameter in hopes that the kernel will last longer this time before the lockup
and/or I catch more details of the lockup when it occurs. If you would prefer
me to try a different variant of this test, please let me know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2287 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
next prev parent reply other threads:[~2018-09-15 0:04 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 [this message]
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-wTIzwdbQOK@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