From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming
Date: Sat, 28 Sep 2019 12:25:32 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1849236026=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id EC04E6E141
for ; Sat, 28 Sep 2019 12:25:32 +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
--===============1849236026==
Content-Type: multipart/alternative; boundary="156967353210.5BDD7F3Eb.4259"
Content-Transfer-Encoding: 7bit
--156967353210.5BDD7F3Eb.4259
Date: Sat, 28 Sep 2019 12:25:32 +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=3D109955
--- Comment #110 from Rodney A Morris ---
(In reply to Rodney A Morris from comment #104)
> (In reply to Mauro Gaspari from comment #103)
> > (In reply to Rodney A Morris from comment #101)
> > > (In reply to Rodney A Morris from comment #99)
> > > > Created attachment 145366 [details]
> > > > apitrace of Hearts of Iron IV hard lock
> > > >=20
> > > > Apitrace from hard lock playing Hearts of Iron IV without Steam. T=
he replay
> > > > from this trace will hard lock the computer, though inconsistently.=
I've
> > > > replayed the trace three times. The replay hard locked computer one=
time.
> > >=20
> > > neofetch from hardlock:
> > >=20
> > > /:-------------:\=20=20=20=20=20=20=20=20=20=20
> > > :-------------------:: --------------------------------=
=20
> > > :-----------/shhOHbmp---:\ OS: Fedora release 30 (Thirty) x=
86_64=20
> > > /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30.x86_64=20
> > > :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20
> > > :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 27 (flatpa=
k)=20
> > > ,------------:MMMd-------- ---: Shell: bash 5.0.7=20
> > > :------------:MMMd------- .---: Resolution: 2560x1440=20
> > > :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20
> > > :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20
> > > :- -------:MMMd--------------: WM Theme: Adwaita=20
> > > :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta [GTK2/3]=
=20
> > > :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=20
> > > :-- :dMNdhhdNMMNo------------; Terminal: tilix=20
> > > :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12) @ 4.000=
GHz=20
> > > :------:://:-------------:: GPU: AMD ATI Radeon RX Vega 56/6=
4=20
> > > :---------------------:// Memory: 2478MiB / 32084MiB=20
> > >=20
> > > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.6
> > >=20
> > > Note: hard lock replayed occurred when the Discord flatpak is also r=
unning.
> >=20
> > I also noticed some errors that pointed to discord in my logs. In my ca=
se
> > discord was installed via .deb package.=20
> > Could you please try and disable hardware acceleration in discord setti=
ngs -
> > appearance menu? Please let me know if it helps or changes anything.=20
> > Thanks!
>=20
> I have disabled hardware acceleration in discord settings to see if that
> improves my experience and report back my results. I am doubtful that it
> will help much. At least on the 5.2.11 kernel, I had lockups with or
> without discord running. Discord running just seemed to make the problem
> appear more consistently.
Another lockup and crash last night of Stellaris with identical dmesg kernel
information as comment 105.
Kernel for this crash: 5.2.17.
Unlike previous attempts, I also had cpupower configured to run the cpu in
performance mode and was running feral gamemode. Although I still wonder i=
f my
hardware has an issue, I am able to run Stellaris without issue under Windo=
ws.
Final Note: Getting an apitrace of my crash under Stellaris is not feasible=
for
two reasons. First, the crash typically happens between 30 minutes and 40
minutes of game play, resulting in a monster trace file. Second, i cannot =
get
apitrace to run correctly with Steam and a 64-bit game, which is necessary
since the crashes happen most frequently in multiplayer.
I am happy to provide more data if someone can point me in the direction to
capture it. Aside from trying the amdgpu-pro drivers, is there anything el=
se I
can try?
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--156967353210.5BDD7F3Eb.4259
Date: Sat, 28 Sep 2019 12:25:32 +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 # 110
on bug 10995=
5
from Rodney A Morris
(In reply to Rodney A Morris from comment #104)
> (In reply to Mauro Gaspari from comment #103)
> > (In reply to Rodney A Morris from comment #101)
> > > (In reply to Rodney A Morris from comment #99)
> > > > Created attachment 145366 [details]
> > > > apitrace of Hearts of Iron IV hard lock
> > > >=20
> > > > Apitrace from hard lock playing Hearts of Iron IV witho=
ut Steam. The replay
> > > > from this trace will hard lock the computer, though inc=
onsistently. I've
> > > > replayed the trace three times. The replay hard locked =
computer one time.
> > >=20
> > > neofetch from hardlock:
> > >=20
> > > /:-------------:\=20=20=20=20=20=20=20=20=20=20
> > > :-------------------:: -----------------------=
---------=20
> > > :-----------/shhOHbmp---:\ OS: Fedora release 30 (=
Thirty) x86_64=20
> > > /-----------omMMMNNNMMD ---: Kernel: 5.2.13-200.fc30=
.x86_64=20
> > > :-----------sMMMMNMNMP. ---: Uptime: 25 mins=20
> > > :-----------:MMMdP------- ---\ Packages: 2202 (rpm), 2=
7 (flatpak)=20
> > > ,------------:MMMd-------- ---: Shell: bash 5.0.7=20
> > > :------------:MMMd------- .---: Resolution: 2560x1440=20
> > > :---- oNMMMMMMMMMNho .----: DE: GNOME 3.32.2=20
> > > :-- .+shhhMMMmhhy++ .------/ WM: GNOME Shell=20
> > > :- -------:MMMd--------------: WM Theme: Adwaita=20
> > > :- --------/MMMd-------------; Theme: Adapta-Nokto-Eta=
[GTK2/3]=20
> > > :- ------/hMMMy------------: Icons: Adwaita [GTK2/3]=
=20
> > > :-- :dMNdhhdNMMNo------------; Terminal: tilix=20
> > > :---:sdNMMMMNds:------------: CPU: Intel i7-6850K (12=
) @ 4.000GHz=20
> > > :------:://:-------------:: GPU: AMD ATI Radeon RX =
Vega 56/64=20
> > > :---------------------:// Memory: 2478MiB / 32084=
MiB=20
> > >=20
> > > OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1=
.6
> > >=20
> > > Note: hard lock replayed occurred when the Discord flatpak =
is also running.
> >=20
> > I also noticed some errors that pointed to discord in my logs. In=
my case
> > discord was installed via .deb package.=20
> > Could you please try and disable hardware acceleration in discord=
settings -
> > appearance menu? Please let me know if it helps or changes anythi=
ng.=20
> > Thanks!
>=20
> I have disabled hardware acceleration in discord settings to see if th=
at
> improves my experience and report back my results. I am doubtful that=
it
> will help much. At least on the 5.2.11 kernel, I had lockups with or
> without discord running. Discord running just seemed to make the prob=
lem
> appear more consistently.
Another lockup and crash last night of Stellaris with identical dmesg kernel
information as comment 105.
Kernel for this crash: 5.2.17.
Unlike previous attempts, I also had cpupower configured to run the cpu in
performance mode and was running feral gamemode. Although I still wonder i=
f my
hardware has an issue, I am able to run Stellaris without issue under Windo=
ws.
Final Note: Getting an apitrace of my crash under Stellaris is not feasible=
for
two reasons. First, the crash typically happens between 30 minutes and 40
minutes of game play, resulting in a monster trace file. Second, i cannot =
get
apitrace to run correctly with Steam and a 64-bit game, which is necessary
since the crashes happen most frequently in multiplayer.
I am happy to provide more data if someone can point me in the direction to
capture it. Aside from trying the amdgpu-pro drivers, is there anything el=
se I
can try?
You are receiving this mail because:
- You are the assignee for the bug.
=
--156967353210.5BDD7F3Eb.4259--
--===============1849236026==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs
--===============1849236026==--