Bug 82791

Summary: GPU lock when using "Death Dance" in Tales of Maj'Eyal
Product: Mesa Reporter: TheLetterN <bugzilla.20.kamdrimar>
Component: Drivers/Gallium/r600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: major    
Priority: medium CC: bugzilla.20.kamdrimar
Version: 10.2   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: dmesg showing GPU lock
glxinfo
journalctl -k --lines=1000
Xorg.0.log

Description TheLetterN 2014-08-19 00:47:00 UTC 
Created attachment 104850 [details]
dmesg showing GPU lock

Symptoms: 
GPU locks and attempts to recover (screen goes black) and locks again upon recovery. Any further attempt to use X11 (even restarting it) locks the GPU, and system must be rebooted to use X11 again.

Steps to reproduce:
1) Download Tales of Maj'Eyal 1.2.3 full for Linux 64-bit - http://te4.org/download
2) Extract the game to a convenient location.
3) Run the t-engine binary from the base game directory, then exit the game.
4) Download a gzip of a character I created - - and extract to: ~/.t-engine/4.0/tome/save/
5) Run t-engine again, load the save game "Pennies".
6) Use the ability "Death Dance" in game.

(If for some reason my save won't work, you need to create a Berserker class character in-game, get it to level 8 and 28 strength, and unlock Death Dance.)

Workarounds attempted:

use different window manager/DE - Failed, bug is reproducible in KDE4, KDE5, Awesome, and Enlightenment 18
pass radeon.audio=0 to kernel command line at boot - Failed, no effect
pass radeon.dpm=0 to kernel - Failed, screen now stays black after GPU lock

Note: this bug may be related to other GPU locks I've been experiencing with Mesa 10.2.x, but this is the only repeatable instance of it so far.
Comment 1 TheLetterN 2014-08-19 00:47:50 UTC 
Created attachment 104851 [details]
glxinfo
Comment 2 TheLetterN 2014-08-19 00:51:25 UTC 
Created attachment 104852 [details]
journalctl -k --lines=1000
Comment 3 TheLetterN 2014-08-19 00:53:18 UTC 
Created attachment 104853 [details]
Xorg.0.log

I couldn't find any useful debugging information in Xorg.0.log, but I'm including it just in case.
Comment 4 TheLetterN 2014-08-19 00:55:59 UTC 
Sorry, forgot to include the link to my save game in step 4:

http://s000.tinyupload.com/index.php?file_id=67207270324448074311
Comment 5 TheLetterN 2014-08-21 23:14:48 UTC 
Comment on attachment 104851 [details]
glxinfo

Update: This bug is still present in mesa 10.2.6
Comment 6 GitLab Migration User 2019-09-18 19:16:53 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/519.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.