From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 110674] Crashes / Resets From AMDGPU / Radeon VII
Date: Sat, 12 Oct 2019 23:34:19 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1352762270=="
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 D14C06E0E2
for ; Sat, 12 Oct 2019 23:34:19 +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
--===============1352762270==
Content-Type: multipart/alternative; boundary="157092325910.c7ff3A1.30731"
Content-Transfer-Encoding: 7bit
--157092325910.c7ff3A1.30731
Date: Sat, 12 Oct 2019 23:34:19 +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=3D110674
--- Comment #161 from Gargoyle ---
Hi there. I've been trying to solve some lockups and pauses with my system =
and
have just read this entire thread.=20
The good news is that I am another Radeon VII owner having the same problems
and I am willing to do whatever I can to help.
My current situation is:-
- I'm running dual 2560x1440@60Hz via display port.
- I am running the beta of ubuntu 19:10 (Linux ryzen1910 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux).
- I don't push the R:VII at all under Linux. I boot into Windows 10 to play
games.
- I have disabled IOMMU in BIOS/EFI. With IOMMU enabled things are MUCH wor=
se.
- My system is mostly stable. If the displays blank, sometimes after waking
them I get the 15-30 second freeze. Then the "amdgpu [powerplay] Failed..."
messages and then everything continues ok. I can semi-reliably recreate thi=
s by
using the "xset dpms force off" command someone posted earlier. I've not
managed to find any kind of pattern yet, but 8 out of 10 times running that
command and then waking the system with a keypress/mouse click will cause t=
he
freeze.
- I use X11 and not wayland. Not sure that is significant, but with Ubuntu
19:10 it seems wayland is started temporarily and then stopped during boot /
starting gdm. If I enable IOMMU my GDM login screen will be completely corr=
upt.
However, if I press enter (to select my user) and enter my password, my X11
gnome session starts. Although there are LOTS of pauses and warnings and er=
rors
all over the place in "journalctl -f".
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--157092325910.c7ff3A1.30731
Date: Sat, 12 Oct 2019 23:34:19 +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
Comm=
ent # 161
on bug 11067=
4
from Gargoyle
Hi there. I've been trying to solve some lockups and pauses wi=
th my system and
have just read this entire thread.=20
The good news is that I am another Radeon VII owner having the same problems
and I am willing to do whatever I can to help.
My current situation is:-
- I'm running dual 2560x1440@60Hz via display port.
- I am running the beta of ubuntu 19:10 (Linux ryzen1910 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux).
- I don't push the R:VII at all under Linux. I boot into Windows 10 to play
games.
- I have disabled IOMMU in BIOS/EFI. With IOMMU enabled things are MUCH wor=
se.
- My system is mostly stable. If the displays blank, sometimes after waking
them I get the 15-30 second freeze. Then the "amdgpu [powerplay] Faile=
d..."
messages and then everything continues ok. I can semi-reliably recreate thi=
s by
using the "xset dpms force off" command someone posted earlier. I=
've not
managed to find any kind of pattern yet, but 8 out of 10 times running that
command and then waking the system with a keypress/mouse click will cause t=
he
freeze.
- I use X11 and not wayland. Not sure that is significant, but with Ubuntu
19:10 it seems wayland is started temporarily and then stopped during boot /
starting gdm. If I enable IOMMU my GDM login screen will be completely corr=
upt.
However, if I press enter (to select my user) and enter my password, my X11
gnome session starts. Although there are LOTS of pauses and warnings and er=
rors
all over the place in "journalctl -f".
You are receiving this mail because:
- You are the assignee for the bug.
=
--157092325910.c7ff3A1.30731--
--===============1352762270==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============1352762270==--