| Bug ID | 98520 |
|---|---|
| Summary | System randomly crashes / freezes while playing certain games |
| Product | Mesa |
| Version | 12.0 |
| Hardware | x86-64 (AMD64) |
| OS | All |
| Status | NEW |
| Severity | blocker |
| Priority | medium |
| Component | Drivers/Gallium/radeonsi |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | sonichedgehog_hyperblast00@yahoo.com |
| QA Contact | dri-devel@lists.freedesktop.org |
Created attachment 127650 <=
a href=3D"attachment.cgi?id=3D127650&action=3Dedit" title=3D"var/log/me=
ssages">[details]
var/log/messages
Starting approximately a week ago, I experience system crashes during which=
the
system suddenly freezes and becomes completely unresponsive. The crashes are
random, and I would estimate them at a probability of one per hour.
They appear to take place while playing certain games: In my case I noticed
this with The Dark Mod (Doom 3 / idTech 4 engine). Although this is uncerta=
in
and barely verified, using OpenGL 3.1 for KDE desktop compositing may also
provoke the crashes, whereas using OpenGL 2.0 does not.
My operating system is openSUSE Tumbleweed x64 (always latest packages). Ke=
rnel
4.8.4-1, Mesa 12.0.3, Gallium 0.4 on AMD PITCAIRN (DRM 2.46.0, LLVM 3.8.1).=
My
video card is a Radeon R7 370 Gigabyte. Attached are: var/log/messages (tod=
ay
only), Xorg.log, xsession-errors. The last crash took place somewhere after
9PM.
Created attachment 127652 [details]
xsession-errors
What components did you update that caused the regression (mes= a, kernel, ddx, etc.)?
(In reply to Alex Deucher from comment #3) As openSUSE Tumbleweed updates a lot of packages at once, I cannot say with certainty. I believe it might have started happening after I switched from Kernel 4.7 to 4.8, but as the issue is very probabilistic as well as risky = to experiment with it's difficult to tell.
(In reply to MirceaKitsune from comment #4) > (In reply to Alex Deucher from comment #3) >=20 > As openSUSE Tumbleweed updates a lot of packages at once, I cannot say= with > certainty. I believe it might have started happening after I switched = from > Kernel 4.7 to 4.8, but as the issue is very probabilistic as well as r= isky > to experiment with it's difficult to tell. Can you try rolling back to previous packages on a per-component basis to s= ee which one caused the regression. Most likely a kernel or mesa change.
| What | Removed | Added |
|---|---|---|
| Priority | medium | high |
(In reply to Alex Deucher from comment #5) openSUSE Tumbleweed is a rolling release distribution; All system packages = are updated and tested together, and running them in untested configurations co= uld break my machine... the old ones are also removed from repository I believe. Since this is my main computer, I can't take such a risk unfortunately.
Created attachment 127654 [details]
Output of "journalctl --no-pager | grep radeon"
Surely there are log files containing information about which = packages were updated from which version to which version when.
(In reply to Michel D=C3=A4nzer from comment #8) I believe YaST / zypper has a log, though I'm not sure how to export it all= to a single text file. It might not help much however: I only remember when the problem started with approximation, and the packages I had back then were l= ong since removed from the repository.
Created attachment 127664 [details]
Output of "journalctl --no-pager"
I was asked for the full output of "journalctl --no-pager" somewh=
ere else,
without the "| grep radeon" part. I will post that here as well.<=
/pre>
Yes. My Radeon R7 370 graphics card by MSI is unstable with th=
e 4.8 kernel from
Fedora 24. There are resets and flickers every few seconds
The work around is to install and boot on the 4.7 kernel from Fedora 23.
The kernel 4.9.0-0.rc7 has no change in behavior that I can se= e.
I would like to confirm this bug. Since a world update yesterd= ay, 3D acceleration has become unusable due to random freezes. Just like MirceaKitsune, I am running on KDE (Plasma 5.8.3) and am on a rolling relea= se distribution (Gentoo). I have tried several kernel, Mesa and libdrm version= s, but the freezes prevail. After a freeze occurs, I can SSH into my system and it is otherwise respons= ive; except for being unable to kill the X server or display manager (sddm). Switching KWin's rendering path to XRender prevents hangs from occurring wh= en on the desktop; the OpenGL 3.3 and 2.0 rendering paths will provoke hangs. When my system hangs, dmesg shows no related messages at all; Xorg.0.log sh= ows nothing out of the ordinary either. Any suggestions on how to obtain useful debugging information is welcomed. My system information is as follows: Linux kernel version: 4.9.0 Mesa version: 13.0.2 LLVM version: 3.9.0-rc1 libdrm version: 2.4.76 Video card: RX 460 4GB Processor: Intel Core i7-5775C
I don't know whether my issue is the same, but what happens to= me is that with a *lot* of games I have (usually those built with Unity) the screen will si= mply freeze after only a minute or two. Sound continues, and I can alt-tab away= and kill -9 the process. It's happening with so many of my games that I really= am incredibly frustrated. Unfortunately I don't really know how to debug or troubleshoot, but will gladly follow any steps required to provide informat= ion. I am also on openSUSE Tumbleweed (rolling release) 64-bit, with a Radeon R7= 370 card. Mesa 13.0.2 xf86-video-ati 7.8.0 llvm 3.8 Kernel 4.8.14 KDE Plasma 5.8.4
Another confirmation. In my case it's usually trigered by the browsers ( FF, Chrome, Pale Moon ) = when HW accelleration is enabled. In FF/Pale Moon there's no obvious cause, while in Chrome it's usually the scrolling which triggers the freeze. Gaming wise, while I don't play much at all, I did test SuperTux Kart. In both cases freezing is completelly random, eg. no specific website, or specific location/track in STK can be isolated as the trigger. Also, sometimes I just get the application in question to freeze, and somet= imes the complete system locks up ( everything frozen, except for the mouse poin= ter which can be moved ). Again, both are random, with the only difference being that if DRI3 is used, the complete lockup seems to happen more often than the app-only freeze. Frequency: Either stable for a single day at max, or freeze occurs back-to-back follow= ing a reboot ( after 5 or 6 times in a row I usually give up and switch to anot= her machine ).=20 Other details: - Machine can be accessed through SSH, and essentialy runs ( eg. Audaciuos still plays ). - X cannot be killed/restarted - Nothing in dmesg/Xorg.log/syslog etc nor in applications ( FF, STK... ) stdout - Kernel makes no difference as it seems, 4.8.x -- 4.9.0, debian pkg or self-compiled vanilla. System: - XFX RX460 4GB - Debian Stretch ( testing ) - Mesa 13.02, Gallium 0.4, DRM 3.8.0, LLVM 3.9.1, Linux 4.9 - Xorg 1.19 - XFCE 4.12 ( xfwm4 from git, with OpenGL compositing enabled ) I'll test the 4.7 kernel, and ( if I manage to roll back to ) older Mesa versions in the following days and report back.
I have noticed the same behaviour exactly after update llvm fr= om 3.9.0 to 3.9.1 Gentoo, Radeon r9 280x kernel-4.9 mesa-13.0.2 libdrm-2.4.74
Created attachment 128671 [details]
dmesg output following a freeze, running linux 4.7.8
Linux 4.7 is a no go.=20
However there was a dmesg output ( attached ).=20
Interesting bit ( presumably right after the crash/freeze ):
[ 203.698277] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0e7a0801
[ 203.698284] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR=20=
=20
0x097EA3CF
[ 203.698285] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0B008001
[ 203.698287] VM fault (0x01, vmid 5) at page 159294415, write from 'TC2'
(0x54433200) (8)
[ 203.698295] amdgpu 0000:01:00.0: GPU fault detected: 147 0x0e920401
[ 203.698296] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR=20=
=20
0x097EA3DC
[ 203.698298] amdgpu 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS
0x0B008001
...snip...
I just upgraded from kernel 4.8.14 to 4.9 and the same symptom= s persist, reproducible always.
Flip: just out of curiousity, have you looked for heat issues = on your system? I had very similar problems and they were due to my system overheating (block= ed fan exhaust)