From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups
Date: Sun, 02 Jul 2017 00:22:48 +0000 [thread overview]
Message-ID: <bug-101672-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2517 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101672
Bug ID: 101672
Summary: radeonsi: 3D engines causing frequent GPU lockups
Product: Mesa
Version: 17.1
Hardware: Other
OS: All
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: sonichedgehog_hyperblast00@yahoo.com
QA Contact: dri-devel@lists.freedesktop.org
A GPU lockup has once again been introduced in Mesa and / or the RadeonSI
driver. As is usual with this sort of thing, the image immediately freezes in
place while audio stops and every form of input becomes unresponsive (including
the NumLock / CapsLock keyboard leds), the only option being to power the
machine off and back on. I started noticing this crash roughly a month ago
after a distribution upgrade (openSUSE Tumbleweed).
The crash only appears to be caused by 3D rendering. It's probabilistic but
very frequent. It is triggered by a variety of game engines, and I've noticed
it with at least the following ones:
- Blender 3D: When opening certain scenes in Blender and going into Weight
Paint mode, the system is bound to crash in at most 5 minutes of usage.
- Second Life: Linux native viewers for Second Life also trigger this, I
believe somewhere between 5 and 30 minutes estimate.
- Xonotic (Darkplaces engine): Starting a game will freeze the machine anywhere
between instantly (the moment a game starts) and 30 minutes at most.
- The Dark Mod (idTech 4 engine): The same freeze will occur when playing
TheDarkMod, anywhere between instantly and roughly 10 minutes at most.
- MineCraft: The native version of Minecraft can also trigger the crash, after
at most 1 hour of playing a game especially on servers with a lot of geometry.
My OS is openSUSE Tumbleweed x64. My current Mesa version is 17.1.3, I can
confirm first noticing this in 17.1.1, but I don't know if the issue was
introduced in 17.1.0 or prior. My video card is a Radeon R7 370 (Gigabyte),
Pitcairn Islands GPU, GCN 1.0, RadeonSI. Official product page:
http://www.gigabyte.com/products/product-page.aspx?pid=5469
Please help to address this issue soon: I am unable to use several applications
due to the risk they pose to my computer! Logs will be attached soon.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3965 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 reply other threads:[~2017-07-02 0:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-02 0:22 bugzilla-daemon [this message]
2017-07-02 0:23 ` [Bug 101672] radeonsi: 3D engines causing frequent GPU lockups bugzilla-daemon
2017-07-02 0:24 ` bugzilla-daemon
2017-07-02 0:24 ` bugzilla-daemon
2017-07-02 0:25 ` bugzilla-daemon
2017-07-02 0:25 ` bugzilla-daemon
2017-07-02 0:26 ` bugzilla-daemon
2017-07-02 15:24 ` bugzilla-daemon
2017-07-11 22:13 ` bugzilla-daemon
2017-07-24 11:59 ` bugzilla-daemon
2017-07-26 22:10 ` bugzilla-daemon
2017-07-26 22:11 ` bugzilla-daemon
2017-07-26 22:12 ` bugzilla-daemon
2017-07-26 22:12 ` bugzilla-daemon
2017-07-26 22:13 ` bugzilla-daemon
2017-07-26 22:13 ` bugzilla-daemon
2017-07-26 22:14 ` bugzilla-daemon
2017-07-26 22:39 ` bugzilla-daemon
2017-07-27 14:52 ` bugzilla-daemon
2017-07-29 13:31 ` bugzilla-daemon
2017-08-01 12:17 ` bugzilla-daemon
2017-08-04 12:33 ` bugzilla-daemon
2018-02-22 0:06 ` bugzilla-daemon
2018-02-22 0:07 ` bugzilla-daemon
2018-02-22 7:34 ` bugzilla-daemon
2018-02-26 21:28 ` bugzilla-daemon
2018-02-27 12:02 ` bugzilla-daemon
2018-03-09 21:39 ` bugzilla-daemon
2018-03-09 21:45 ` 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-101672-502@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