Bug 75371 - System hang with kernel 3.13 while playing Left 4 Dead 2
Summary: System hang with kernel 3.13 while playing Left 4 Dead 2
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-22 15:42 UTC by RandyRowboat
Modified: 2014-07-23 17:43 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description RandyRowboat 2014-02-22 15:42:51 UTC
Hey,

when playing Left 4 Dead 2 (only thing I tested) for a long time, the system randomly hangs. Happens maybe once an hour or so. I think it's not only X that crashes, but the whole kernel. Can't do sysrq, poweroff, restart..

I upgraded to the testing 3.13 kernel in archlinux, that's when I experienced it the first time. So I reverted back to 3.12 and everything was fine again. Now that 3.13 hit the core/stable repo I gave it another try and it started crashing again.

linux 3.13.4 (also 3.13, 3.13.1, 3.13.2 <- I'm not sure if it happened with all of these, but most likely it did )
ati hd 5850 (Cypress PRO)
mesa-git - r600g ( Mesa 10.2.0-devel (git-9b2fe7c) )

dpm was also manually enabled with 3.12 and before, so it's likely not related to that. Never had problems with it.
Comment 1 Alex Deucher 2014-02-22 17:43:37 UTC
Can you bisect?
Comment 2 RandyRowboat 2014-02-22 17:49:46 UTC
No, that would take forever and I have don't that much time ;)
Comment 3 Michel Dänzer 2014-02-24 06:11:05 UTC
(In reply to comment #0)
> dpm was also manually enabled with 3.12 and before, so it's likely not
> related to that.

I think it's still worth testing if the problem occurs with DPM explicitly disabled via radeon.dpm=0.

(In reply to comment #2)
> No, that would take forever and I have don't that much time ;)

Please reconsider. For every gaming session, you should be able to declare at least one commit good or bad. It shouldn't take more than a dozen or so tests to isolate the problem with git bisect.
Comment 4 RandyRowboat 2014-07-23 17:42:40 UTC
ok, I played it a bit again and it seems to be fixed since ~3.15 .


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.