From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105227] [SUMO][TURKS] observer game cause GPU lockup
Date: Fri, 23 Feb 2018 14:29:49 +0000 [thread overview]
Message-ID: <bug-105227-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2461 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105227
Bug ID: 105227
Summary: [SUMO][TURKS] observer game cause GPU lockup
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: russianneuromancer@ya.ru
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 137557
--> https://bugs.freedesktop.org/attachment.cgi?id=137557&action=edit
dmesg from launch on Radeon HD 6650M
Hi!
Game "observer" cause GPU lockup on Radeon HD 6620G and 6650M GPUs with Mesa
18.1 4562a7b0e82bf664 - dmesg from two launch attempts is attached. Graphical
settings is all set to minimal, all visual effects is disabled.
[ 386.552620] radeon 0000:01:00.0: ring 0 stalled for more than 10288msec
[ 386.552638] radeon 0000:01:00.0: GPU lockup (current fence id
0x000000000000147b last fence id 0x0000000000001487 on ring 0)
[ 387.064666] radeon 0000:01:00.0: ring 0 stalled for more than 10800msec
[ 387.064683] radeon 0000:01:00.0: GPU lockup (current fence id
0x000000000000147b last fence id 0x0000000000001487 on ring 0)
[ 387.416749] radeon 0000:01:00.0: ring 3 stalled for more than 10036msec
[ 387.416765] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000001001 last fence id 0x0000000000001002 on ring 3)
[ 387.576741] radeon 0000:01:00.0: ring 0 stalled for more than 11312msec
[ 387.576758] radeon 0000:01:00.0: GPU lockup (current fence id
0x000000000000147b last fence id 0x0000000000001487 on ring 0)
[ 387.928798] radeon 0000:01:00.0: ring 3 stalled for more than 10548msec
[ 387.928814] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000001001 last fence id 0x0000000000001002 on ring 3)
To reproduce GPU lockup:
1. Launch game like this: MESA_GL_VERSION_OVERRIDE=4.3
MESA_GLSL_VERSION_OVERRIDE=430 %command% (otherwise it crash before launch)
2. Select New game, wait until loading completed.
3. After loading completed press space or left mouse button.
Hardware:
Acer Aspire 7560G, AMD A8-3500M
AMD Radeon HD 6620G iGPU, AMD Radeon HD 6650M dGPU.
Software:
Kubuntu 17.10 x86_64, Linux 4.15.5, Mesa 18.1 4562a7b0e82bf664
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4004 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:[~2018-02-23 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 14:29 bugzilla-daemon [this message]
2018-02-23 14:30 ` [Bug 105227] [SUMO][TURKS] observer game cause GPU lockup bugzilla-daemon
2019-09-18 19:25 ` 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-105227-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