From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
Date: Mon, 02 Apr 2018 12:15:49 +0000 [thread overview]
Message-ID: <bug-105425-502-GwYiy1XHZK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105425-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1406 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #14 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
(In reply to iive from comment #13)
Like I said, I don't currently believe this is a hardware defect: My video card
isn't even 3 years old. It's a card from Gigabyte which makes high quality
products. The temperature of the GPU is within bounds at all times (45°C to
70°C). Its GPU clock seems to be at the right frequency, whereas the memory
clock appears to be at 1/3 the supported frequency so it already is
under-clocked and more stable! Also why does only 3D ever produce the freeze,
even simple scenes that don't stress either the GPU nor the VRAM... whereas 2D
never does it even when it's intensive (eg: games, desktop compositing)?
If people believe hardware hasn't been ruled out, please suggest a GPU
stressing tool for Linux (I use openSUSE Tumbleweed) which you believe is
adequate for this situation. I no longer have Windows and can't redo my entire
setup by installing another OS, this is my main desktop on which I do my work
and activities.
I still think this is related to a driver or kernel vulnerability of some sort.
Please let me know which logs I can post or what else I can monitor to confirm
this and see exactly where and how it's happening.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2269 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
next prev parent reply other threads:[~2018-04-02 12:15 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 [this message]
2018-04-04 1:06 ` bugzilla-daemon
2018-04-04 17:36 ` bugzilla-daemon
2018-04-08 22:47 ` bugzilla-daemon
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-GwYiy1XHZK@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.