dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming
Date: Thu, 24 Oct 2019 03:12:28 +0000	[thread overview]
Message-ID: <bug-109955-502-IlsN1KFZj3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109955-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1163 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=109955

--- Comment #120 from blppt@yahoo.com ---
I dont have anything to attach here, but same issue here, ubuntu 19.04, kernel
5.4-rc3, vega64 W/C, Mesa 19.3.0 -- it only seems to occur with DXVK and not
D9VK for some reason.

Example: GW2 (DX9 game) will work perfectly under heavy load in WvW with
massive zergs for hours with no crash, but FFXIV (DX11) will always lock the
entire system up after a time.

That being said, when you force the top clock using

echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level

and

echo 7 > /sys/class/drm/card0/device/pp_dpm_sclk

FFXIV no longer locks the system at all. It does eat up a good deal more watts
according to my UPS meter though, so resetting to auto is necessary IMHO.

So, it sounds like you guys are on the right track with the whole "power
management" thing being the culprit. Just wanted to add my experience to this.

(and yes, echoing the guy above, the exact same system is stable in windows 10,
so its not a hardware issue).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1930 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-10-24  3:12 UTC|newest]

Thread overview: 147+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-109955-502@http.bugs.freedesktop.org/>
2019-03-11 11:27 ` [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming bugzilla-daemon
2019-03-22 20:01 ` bugzilla-daemon
2019-03-22 20:02 ` bugzilla-daemon
2019-03-22 20:02 ` bugzilla-daemon
2019-04-11  6:37 ` bugzilla-daemon
2019-04-12 21:37 ` bugzilla-daemon
2019-04-12 22:10 ` bugzilla-daemon
2019-04-13  9:34 ` bugzilla-daemon
2019-04-13  9:41 ` bugzilla-daemon
2019-04-13  9:49 ` bugzilla-daemon
2019-04-13  9:52 ` bugzilla-daemon
2019-04-13 11:34 ` bugzilla-daemon
2019-04-13 13:19 ` bugzilla-daemon
2019-04-13 13:45 ` bugzilla-daemon
2019-04-15 12:51 ` bugzilla-daemon
2019-04-25 19:44 ` bugzilla-daemon
2019-04-28 16:33 ` bugzilla-daemon
2019-04-29  1:15 ` bugzilla-daemon
2019-04-29 10:41 ` bugzilla-daemon
2019-04-29 11:35 ` bugzilla-daemon
2019-04-29 11:37 ` bugzilla-daemon
2019-04-29 13:52 ` bugzilla-daemon
2019-05-24  5:12 ` bugzilla-daemon
2019-05-24 12:24   ` sylvain.bertrand
2019-05-24 12:25 ` bugzilla-daemon
2019-05-24 13:44 ` bugzilla-daemon
2019-06-03  8:07 ` bugzilla-daemon
2019-06-03 20:10 ` bugzilla-daemon
2019-06-04 21:43 ` bugzilla-daemon
2019-06-05  6:34 ` bugzilla-daemon
2019-06-09 18:46 ` bugzilla-daemon
2019-06-10 17:13 ` bugzilla-daemon
2019-06-13 21:04 ` bugzilla-daemon
2019-06-13 21:04 ` bugzilla-daemon
2019-06-14  5:48 ` bugzilla-daemon
2019-06-14 14:33 ` bugzilla-daemon
2019-07-06  9:30 ` bugzilla-daemon
2019-07-07  5:31 ` bugzilla-daemon
2019-07-07 17:41   ` sylvain.bertrand
2019-07-07 10:55 ` bugzilla-daemon
2019-07-07 17:42 ` bugzilla-daemon
2019-07-08  5:29 ` bugzilla-daemon
2019-07-09 14:29 ` bugzilla-daemon
2019-07-09 18:05   ` sylvain.bertrand
2019-07-09 18:06 ` bugzilla-daemon
2019-07-10  7:25 ` bugzilla-daemon
2019-07-10  8:03 ` bugzilla-daemon
2019-07-10  8:19 ` bugzilla-daemon
2019-07-10  8:26 ` bugzilla-daemon
2019-07-10  9:41 ` bugzilla-daemon
2019-07-10 14:44 ` bugzilla-daemon
2019-07-10 18:42 ` bugzilla-daemon
2019-07-12 15:26 ` bugzilla-daemon
2019-07-13 17:22 ` bugzilla-daemon
2019-07-16  8:28 ` bugzilla-daemon
2019-07-17  3:34 ` bugzilla-daemon
2019-07-17 16:02   ` sylvain.bertrand
2019-07-17 16:02 ` bugzilla-daemon
2019-07-18  2:30 ` bugzilla-daemon
2019-07-18 13:44   ` sylvain.bertrand
2019-07-18 13:44 ` bugzilla-daemon
2019-07-19  0:12 ` bugzilla-daemon
2019-07-22  5:19 ` bugzilla-daemon
2019-07-23 16:25 ` bugzilla-daemon
2019-07-23 16:30 ` bugzilla-daemon
2019-07-23 17:14 ` bugzilla-daemon
2019-07-23 20:17   ` sylvain.bertrand
2019-07-23 20:18 ` bugzilla-daemon
2019-07-24  4:14 ` bugzilla-daemon
2019-07-24 13:08   ` sylvain.bertrand
2019-07-24 13:09 ` bugzilla-daemon
2019-07-24 14:27 ` bugzilla-daemon
2019-07-24 14:41 ` bugzilla-daemon
2019-07-24 14:55   ` sylvain.bertrand
2019-07-24 14:56 ` bugzilla-daemon
2019-07-27 11:28 ` bugzilla-daemon
2019-07-27 13:19   ` sylvain.bertrand
2019-07-27 13:19 ` bugzilla-daemon
2019-07-27 17:32 ` bugzilla-daemon
2019-07-28  3:14 ` bugzilla-daemon
2019-08-03 13:35 ` bugzilla-daemon
2019-08-03 16:54 ` bugzilla-daemon
2019-08-03 17:43 ` bugzilla-daemon
2019-08-03 18:46 ` bugzilla-daemon
2019-08-04  5:05 ` bugzilla-daemon
2019-08-04 14:18 ` bugzilla-daemon
2019-08-04 16:17 ` bugzilla-daemon
2019-08-05  5:54 ` bugzilla-daemon
2019-08-05  6:16 ` bugzilla-daemon
2019-08-07  9:53 ` bugzilla-daemon
2019-08-11  9:31 ` bugzilla-daemon
2019-08-12  2:50 ` bugzilla-daemon
2019-08-12  8:16 ` bugzilla-daemon
2019-08-12 14:10 ` bugzilla-daemon
2019-08-13 15:59 ` bugzilla-daemon
2019-08-13 16:19 ` bugzilla-daemon
2019-08-30 19:01 ` bugzilla-daemon
2019-08-31  1:00 ` bugzilla-daemon
2019-08-31  5:21 ` bugzilla-daemon
2019-08-31 22:38 ` bugzilla-daemon
2019-09-01 22:49 ` bugzilla-daemon
2019-09-02  7:48 ` bugzilla-daemon
2019-09-02 10:07 ` bugzilla-daemon
2019-09-04 20:41 ` bugzilla-daemon
2019-09-07  3:48 ` bugzilla-daemon
2019-09-07  3:50 ` bugzilla-daemon
2019-09-12 20:08 ` bugzilla-daemon
2019-09-15  1:16 ` bugzilla-daemon
2019-09-15  1:20 ` bugzilla-daemon
2019-09-15  1:21 ` bugzilla-daemon
2019-09-15  4:35 ` bugzilla-daemon
2019-09-21  2:05 ` bugzilla-daemon
2019-09-23  2:49 ` bugzilla-daemon
2019-09-23  3:06 ` bugzilla-daemon
2019-09-26 10:37 ` bugzilla-daemon
2019-09-26 12:56 ` bugzilla-daemon
2019-09-28  7:02 ` bugzilla-daemon
2019-09-28 11:05 ` bugzilla-daemon
2019-09-28 12:25 ` bugzilla-daemon
2019-10-03  9:57 ` bugzilla-daemon
2019-10-05 10:12 ` bugzilla-daemon
2019-10-05 12:02 ` bugzilla-daemon
2019-10-19 21:26 ` bugzilla-daemon
2019-10-19 21:27 ` bugzilla-daemon
2019-10-19 21:28 ` bugzilla-daemon
2019-10-21 16:24 ` bugzilla-daemon
2019-10-23  1:52 ` bugzilla-daemon
2019-10-23  8:51 ` bugzilla-daemon
2019-10-24  3:12 ` bugzilla-daemon [this message]
2019-10-24  4:58 ` bugzilla-daemon
2019-10-24  9:09 ` bugzilla-daemon
2019-10-24  9:10 ` bugzilla-daemon
2019-10-29 19:00 ` bugzilla-daemon
2019-11-05 18:01 ` bugzilla-daemon
2019-11-06  2:46 ` bugzilla-daemon
2019-11-06  9:49 ` bugzilla-daemon
2019-11-06 10:23 ` bugzilla-daemon
2019-11-06 17:32 ` bugzilla-daemon
2019-11-06 18:32 ` bugzilla-daemon
2019-11-06 19:26 ` bugzilla-daemon
2019-11-07 10:25 ` bugzilla-daemon
2019-11-07 16:50 ` bugzilla-daemon
2019-11-12 11:03 ` bugzilla-daemon
2019-11-17 14:24 ` bugzilla-daemon
2019-11-17 17:13 ` bugzilla-daemon
2019-11-17 17:18 ` [Bug 109955] amdgpu [RX Vega 64] system freeze while gaming (VSYNC enabled) bugzilla-daemon
2019-11-20  7:52 ` 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-109955-502-IlsN1KFZj3@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