| Summary: | Counter Strike Global Offensive: GPU fault after a while | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Christoph Haag <haagch> |
| Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | normal | ||
| Priority: | medium | CC: | daniel, matthew |
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
dmesg
dmesg with graphical output hang R600_DEBUG=ps,vs,gs csgo 2> csgoerr.txt Mass Effect 3 with nine dmesg csgo tahiti |
||
|
Description
Christoph Haag
2015-04-28 16:34:09 UTC
Can you run the program with the environment variable R600_DEBUG=ps,vs,gs and post the output. Created attachment 115456 [details]
dmesg with graphical output hang
It can also have more severe consequences and require a reboot, see dmesg.
I'll use R600_DEBUG=ps,vs,gs next time. It can take quite a while to trigger it, I hope it won't produce too much data.
Created attachment 115459 [details]
R600_DEBUG=ps,vs,gs csgo 2> csgoerr.txt
This time with a 3.19 kernel with ck patches (wanted to see whether gameplay is more smooth with it)
Didn't show a GPU fault in dmesg this time, just started outputting messages like
[ 6556.091663] radeon 0000:01:00.0: ring 0 stalled for more than 10035msec
[ 6556.091668] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000003eaad7 last fence id 0x00000000003eaaf4 on ring 0)
[ 6556.593178] radeon 0000:01:00.0: ring 0 stalled for more than 10536msec
[ 6556.593187] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000003eaad7 last fence id 0x00000000003eaaf4 on ring 0)
[ 6557.094722] radeon 0000:01:00.0: ring 0 stalled for more than 11037msec
[ 6557.094728] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000003eaad7 last fence id 0x00000000003eaaf4 on ring 0)
[ 6557.596237] radeon 0000:01:00.0: ring 0 stalled for more than 11538msec
Created attachment 115981 [details]
Mass Effect 3 with nine
Hm, I tried Mass Effect 3 with nine and got a GPU hang too. Not sure if it's the same. No further log right now, I'll first check whether it's always at the same point (it happened in the intro at the exact moment the reaper shoots, so I think there is something that actually triggers it)
Hasn't happened for a while, will reopen in case it happens again. Unfortunately I'm hit by this as well. Although I can't tell if it's fixed in the latest git. Happened after a few minutes (First try 2 minutes, second try ~30 minutes) of gameplay on my HD 7970 - Tahiti XT. Mesa 10.6.3 Kernel 4.1.2 Arch, up-to-date Game Settings: Global Shadow Quality - High Model / Texture Detail -High Effect Detail - High Shader Detail - Very High Multicore Rendering - Enabled MSAA - 8x FSAA - Enabled Texture Filter - Anisotropic 16x Vsync - Disabled Motion Blur - Enabled Created attachment 117500 [details]
dmesg csgo tahiti
Hi guys, There have been many improvements since this was reported, and I don't see any other reports like this. Is this still happening or can we close this bug? (In reply to Timothy Arceri from comment #8) > Hi guys, > > There have been many improvements since this was reported, and I don't see > any other reports like this. Is this still happening or can we close this > bug? Hi Timothy, I've been playing CSGO frequently on my 7970 with no issues on a recent graphics stack (Linux 4.14.10, Mesa 17.3.1 most recently) and have had no issues. Thus I think this issue can be closed now. -- 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/1217. |
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.