From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 106671] Frequent lock ups for AMD RX 550 graphics card
Date: Sat, 15 Sep 2018 00:04:12 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0083626760=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[IPv6:2610:10:20:722:a800:ff:fe98:4b55])
by gabe.freedesktop.org (Postfix) with ESMTP id 561906E0C6
for ; Sat, 15 Sep 2018 00:04:12 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0083626760==
Content-Type: multipart/alternative; boundary="15369698520.4102.7679"
Content-Transfer-Encoding: 7bit
--15369698520.4102.7679
Date: Sat, 15 Sep 2018 00:04:12 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D106671
--- Comment #16 from Alan W. Irwin ---
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 almos=
t 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 pac=
kage
from Debian Buster for this latest experiment.=20=20
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, b=
ut I
may be missing something since I am no expert so I would appreciate it if y=
ou
took a look.
I have restarted exactly the same direct graphics access test again (with s=
ame
versions of graphics stack packages and your recommended idle=3Dnomwait ker=
nel
parameter in hopes that the kernel will last longer this time before the lo=
ckup
and/or I catch more details of the lockup when it occurs. If you would pre=
fer
me to try a different variant of this test, please let me know.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15369698520.4102.7679
Date: Sat, 15 Sep 2018 00:04:12 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 16
on bug 10667=
1
from Alan W. Irwin
I was beginning to have some hope that the latest direct acces=
s experiment
would prove to be stable. However, just now it locked up again after almos=
t 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 pac=
kage
from Debian Buster for this latest experiment.=20=20
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, b=
ut I
may be missing something since I am no expert so I would appreciate it if y=
ou
took a look.
I have restarted exactly the same direct graphics access test again (with s=
ame
versions of graphics stack packages and your recommended idle=3Dnomwait ker=
nel
parameter in hopes that the kernel will last longer this time before the lo=
ckup
and/or I catch more details of the lockup when it occurs. If you would pre=
fer
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.
=
--15369698520.4102.7679--
--===============0083626760==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0083626760==--