| Bug ID | 91084 |
|---|---|
| Summary | RadeonSI crash while playing World Of Tanks |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/Radeon |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | edzis@inbox.lv |
Computer freezes completely however I can access it via the ssh. Versions are in the files. This is with Ubuntu 14.04 using liquorix kernel and this is the first time I can actually ssh into the machine after crash. Previously tried with Ubuntu 15.04 using kernel 4.1/3.13/3.19/4.0.x all of them crash completely. Versions/syslog/etc. are in the attachments. Please ask if You need more info.
Created attachment 116692 [details]
Photo of bug happening on screen
Created attachment 116693 [details]
Package versions / lspci
If you're using the Gallium nine state tracker, this may be a = duplicate of bug 89713.
Well, might be, once I tried posting to that bug as well, but with rather incomplete info, now I have a lot more and it didn't look like that bug, albeit the reason for bug might be the same. Suggest plz how to proceed further, repost everything to that bug, or ... ?
Hi, I tried to experiment even further, what seems to be odd is that after about 7 minutes it will crash, I don't have to do anything in the game - 7 minutes pass and it hangs. I tried to play simple training area, just waited till training map loaded up, I didn't even move the tank or mouse or anything (game was not even active window), started stopwatch and after 7 and 2 seconds it started to draw crazy lines and 7:07 it crashed completely. Of course this is not in any way scientific test :) It seems quite odd that always 7 minutes and crash. I'm just trying to think, 7 mins, 420 secs, 25200 frames @ 60 fps (which I can't reach). Will try to do more testing with debugging enabled.
Ok, I installed -dbg packages for mesa/radeon, didn't and had no luck using gdb (or I don't know how to use it to debug radeon/mesa drivers), but I had luck getting some debug out of R600_DEBUG. Please note "radeon: The kernel rejected CS, see dmesg for more information." and "radeon: Failed to deallocate virtual address for buffer:" in the R600_DEBUG.txt file. I had 400MB of syslog filled with errors, I took just last 500 lines to upload here. Hope this will help a bit more with solving the issue. Please advise what can I do more.
Created attachment 116962 [details]
syslog (last 500 lines)
Created attachment 116963 [details]
Xorg.log with error at the end
Created attachment 116964 [details]
R600_DEBUG=fs,vs,gs,ps,cs,vm (this one has interesting info at the end)
Created attachment 117071 [details]
A bit different crashlog from archlinux (mesa/radeon git from 11.07.2015)
Hi, I'm glad to report that today I tried playing WOT with latest mesa/radeon and it didn't crash for at least 3 hrs (wine 1.7.44-nine, gallium nine, oibaf ppa). Package versions are as follows: all mesa package versions are 10.7~git1507310730.7830e4~gd~t, radeon driver package version is 7.5.99+git1507301931.09c7cd~gd~t. Not sure if this helped or not, but one thing that I had to change (because I had to free some space temporarily) was to move radeon card to pcie x8 slot, after a week or so I'll move radeon back to x16 slot and will test again. regards Mjasnik
Hi, so I moved back radeon to x16 slot and it works. I played like 2-3 hrs in a row and no crash, it played quite well, except some graphical glitches for shadow and some crappy graphics for couple of seconds at the start of the battle, but the rest is very good. So I guess this problem is gone. As I finally got this working, I didn't update packages, I'll do that later, but my bet is that all will be working. regards Mjasnik
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- 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/drm/amd/issues/622.