All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
Date: Sun, 08 Apr 2018 22:47:14 +0000	[thread overview]
Message-ID: <bug-105425-502-uGmMhVFET1@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105425-502@http.bugs.freedesktop.org/>


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

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

--- Comment #16 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
I have moved on to testing the various kernel parameters available for my
driver and card. As was pointed out by malcolmlewis on the openSUSE forums,
they can be listed with the following commands:

modinfo amdgpu
systool -vm amdgpu

I tested nearly half of them today, almost none made any difference. There were
however a few settings that appeared to influence the frequency of the freeze.
The most notable one of all seems to be the following:

amdgpu.moverate=4

With no parameters changed, the freeze now occurs roughly once per 30 minutes
in Xonotic. With that move rate limited to 4MB/s however, I seemingly reduced
it to only 90 minutes! The FPS will constantly drop and recover, but that makes
sense as this setting explicitly limits the buffer migration rate.

I may test other variables in the days to come, but for now I'm hoping this
offers at least some clue to get things started. My feeling is that the video
card may be slowly loaded with information until something fills up, or perhaps
some events throw too much data in at once and it reaches a bottleneck?

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

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

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

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

  parent reply	other threads:[~2018-04-08 22:47 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-105425-502@http.bugs.freedesktop.org/>
2018-03-13 10:38 ` [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370) bugzilla-daemon
2018-03-25 21:21 ` bugzilla-daemon
2018-03-28  0:20 ` bugzilla-daemon
2018-03-28 23:03 ` bugzilla-daemon
2018-03-30  1:49 ` bugzilla-daemon
2018-04-01 19:53 ` bugzilla-daemon
2018-04-01 23:11 ` bugzilla-daemon
2018-04-02  9:33 ` bugzilla-daemon
2018-04-02 12:15 ` bugzilla-daemon
2018-04-04  1:06 ` bugzilla-daemon
2018-04-04 17:36 ` bugzilla-daemon
2018-04-08 22:47 ` bugzilla-daemon [this message]
2018-04-09 19:43 ` bugzilla-daemon
2018-04-09 20:16 ` bugzilla-daemon
2018-04-09 20:22 ` bugzilla-daemon
2018-04-10  9:13 ` bugzilla-daemon
2018-04-10 11:55 ` bugzilla-daemon
2018-04-12 13:55 ` bugzilla-daemon
2018-04-12 13:56 ` bugzilla-daemon
2018-04-12 13:57 ` bugzilla-daemon
2018-04-12 15:42 ` bugzilla-daemon
2018-04-12 17:02 ` bugzilla-daemon
2018-04-12 17:14 ` bugzilla-daemon
2018-04-13 19:39 ` bugzilla-daemon
2018-04-14 18:41 ` bugzilla-daemon
2018-04-17  9:27 ` bugzilla-daemon
2018-04-17 13:58 ` bugzilla-daemon
2018-04-17 19:10 ` bugzilla-daemon
2018-04-17 20:06 ` bugzilla-daemon
2018-04-18 21:51 ` bugzilla-daemon
2018-04-18 22:43 ` bugzilla-daemon
2018-04-20 14:32 ` bugzilla-daemon
2018-04-20 14:34 ` bugzilla-daemon
2018-04-20 14:34 ` bugzilla-daemon
2018-04-21 11:46 ` bugzilla-daemon
2018-04-24 12:08 ` bugzilla-daemon
2018-04-24 12:13 ` bugzilla-daemon
2018-04-24 12:15 ` bugzilla-daemon
2018-04-24 16:26 ` bugzilla-daemon
2018-04-24 18:34 ` bugzilla-daemon
2018-04-24 19:23 ` bugzilla-daemon
2018-04-24 20:14 ` bugzilla-daemon
2018-04-24 20:25 ` bugzilla-daemon
2018-04-24 20:29 ` bugzilla-daemon
2018-04-25 10:03 ` bugzilla-daemon
2018-04-25 15:28 ` bugzilla-daemon
2018-04-26  0:51 ` bugzilla-daemon
2018-04-26  1:10 ` bugzilla-daemon
2018-04-26 15:23 ` bugzilla-daemon
2018-04-26 20:19 ` bugzilla-daemon
2018-04-29 19:41 ` bugzilla-daemon
2018-04-29 21:37 ` bugzilla-daemon
2018-04-30 11:50 ` bugzilla-daemon
2018-04-30 12:07 ` bugzilla-daemon
2018-04-30 20:59 ` bugzilla-daemon
2018-04-30 21:41 ` bugzilla-daemon
2018-05-01  0:03 ` bugzilla-daemon
2018-05-01 21:06 ` bugzilla-daemon
2018-05-02  0:29 ` bugzilla-daemon
2018-05-02  1:21 ` bugzilla-daemon
2018-05-02  2:55 ` bugzilla-daemon
2018-05-02  9:59 ` bugzilla-daemon
2018-05-02 20:35 ` bugzilla-daemon
2018-05-05 14:24 ` bugzilla-daemon
2018-05-12 22:42 ` bugzilla-daemon
2018-05-29 13:01 ` bugzilla-daemon
2018-05-30 11:36 ` bugzilla-daemon
2018-05-30 12:12 ` bugzilla-daemon
2018-05-30 13:32 ` bugzilla-daemon
2018-05-31 13:00 ` bugzilla-daemon
2018-05-31 21:07 ` bugzilla-daemon
2018-09-01 19:48 ` bugzilla-daemon
2018-12-08 14:53 ` 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-105425-502-uGmMhVFET1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.