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: Sun, 04 Nov 2018 06:40:16 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0385195270=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 1F5506E0AE
for ; Sun, 4 Nov 2018 06:40:16 +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
--===============0385195270==
Content-Type: multipart/alternative; boundary="15413136160.BFa9e7A.16764"
Content-Transfer-Encoding: 7bit
--15413136160.BFa9e7A.16764
Date: Sun, 4 Nov 2018 06:40:16 +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 #34 from Alan W. Irwin ---
I have discovered this box became significantly less stable when there were=
two
users displaying X directly on it (one with startx , one with startx -- :1)=
and
using ctrl-alt-F1 and ctrl-alt-F2 to switch between the two local X servers
that were displaying two different XFCE desktops via the RX 550 graphics ca=
rd.
After moving to that mode of operation we got the following results for upt=
imes
before lockups:
1 day, 2 times
2 days, 1 time
3 days, 1 time
For each of these 4 lockups I could not spot any relevant messages in the l=
og
files. But the substantially shorter uptimes for this method of using this=
box
does appear to confirm there are still issues with the graphics stack for t=
he
RX550. But the graphics content being displayed by the two users is roughly
similar so I don't understand why this mode of operation is so much less st=
able
then if just one user is using the RX 550 while the other is using an
X-terminal. (None of these lockups occurred anywhere near the times we
switched between the two local X servers, but I suppose it is possible that
switching sets up a condition that results in a lockup much later.)
Anyhow, because of the increased instability I gave up on the two local X
servers approach and went back to the one local X server and one X-terminal
approach, and with that approach we got an uptime of a week before the syst=
em
locked up. That lockup occurred tonight, and I have attached a tarball
containing log files that show many NMI error messages associated with that
lockup (but with no reference to the e1000e module this time).
@Michel D=C3=A4nzer: Could you please take a look at these log files and le=
t me know
if this is the best place to report the present lockup?
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15413136160.BFa9e7A.16764
Date: Sun, 4 Nov 2018 06:40:16 +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 # 34
on bug 10667=
1
from Alan W. Irwin
I have discovered this box became significantly less stable wh=
en there were two
users displaying X directly on it (one with startx , one with startx -- :1)=
and
using ctrl-alt-F1 and ctrl-alt-F2 to switch between the two local X servers
that were displaying two different XFCE desktops via the RX 550 graphics ca=
rd.
After moving to that mode of operation we got the following results for upt=
imes
before lockups:
1 day, 2 times
2 days, 1 time
3 days, 1 time
For each of these 4 lockups I could not spot any relevant messages in the l=
og
files. But the substantially shorter uptimes for this method of using this=
box
does appear to confirm there are still issues with the graphics stack for t=
he
RX550. But the graphics content being displayed by the two users is roughly
similar so I don't understand why this mode of operation is so much less st=
able
then if just one user is using the RX 550 while the other is using an
X-terminal. (None of these lockups occurred anywhere near the times we
switched between the two local X servers, but I suppose it is possible that
switching sets up a condition that results in a lockup much later.)
Anyhow, because of the increased instability I gave up on the two local X
servers approach and went back to the one local X server and one X-terminal
approach, and with that approach we got an uptime of a week before the syst=
em
locked up. That lockup occurred tonight, and I have attached a tarball
containing log files that show many NMI error messages associated with that
lockup (but with no reference to the e1000e module this time).
@Michel D=C3=A4nzer: Could you please take a look at these log files an=
d let me know
if this is the best place to report the present lockup?
You are receiving this mail because:
- You are the assignee for the bug.
=
--15413136160.BFa9e7A.16764--
--===============0385195270==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0385195270==--