[Bugme-new] [Bug 41482] New: GPU hanging too fast, declaring wedged

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=41482

           Summary: GPU hanging too fast, declaring wedged
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.0.0-next-20110728+
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - Intel)
        AssignedTo: drivers_video-dri-intel at kernel-bugs.osdl.org
        ReportedBy: error27 at gmail.com
        Regression: No


Mplayer sometimes hangs my graphics card.

[208355.642949] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed...
GPU hung
[208355.642961] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[208357.565873] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed...
GPU hung
[208357.565979] [drm:i915_wait_request] *ERROR* i915_wait_request returns -11
(awaiting 2541803 at 2541800, next 2541804)
[208357.566080] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring
wedged!
[208357.566089] [drm:i915_reset] *ERROR* Failed to reset chip.

Sometimes when I start mplayer, or when I switch to the mplayer window then my
graphics hang.  The mouse still shows up but the windows are stuck.  I can
still switch to the non-graphical TTYs.

I have to reboot to fix it.

Next time when it happens I can mount debugfs.  What information do you want
from /debug/dri/0/i915_error_state?

I can't reproduce this reliably.  I've tried switching back and forth the
mplayer like mad or starting it over and over but I couldn't find an easy way
to trigger it.  But it's not super rare either.

Also looking at the version now, I see that that this kernel is not as recent
as I had thought.  I'll upgrade and see if the problem is still there.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.