[Bug 44342] New: [i915g] GPU hang when running Khronos Webgl test suite

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Dec 31 03:19:03 PST 2011


https://bugs.freedesktop.org/show_bug.cgi?id=44342

             Bug #: 44342
           Summary: [i915g] GPU hang when running Khronos Webgl test suite
    Classification: Unclassified
           Product: Mesa
           Version: git
          Platform: Other
               URL: https://cvs.khronos.org/svn/repos/registry/trunk/publi
                    c/webgl/sdk/tests/webgl-conformance-tests.html
        OS/Version: All
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Gallium/i915g
        AssignedTo: dri-devel at lists.freedesktop.org
        ReportedBy: pavel.ondracka at email.cz


Created attachment 54998
  --> https://bugs.freedesktop.org/attachment.cgi?id=54998
terminal output and backtrace

When running Khronos Webgl test suite there is an occasional crash and gpu
hang. This is not 100% reproducible with one test, sometimes it finishes whole
test run OK, sometimes it hangs really fast. Running glsl functions subtests
few time is a row reproduces it here always.

[  534.984024] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed...
GPU hung
[  534.984036] [drm] capturing error event; look for more information in
/debug/dri/0/i915_error_state
[  534.987135] [drm:i915_reset] *ERROR* Failed to reset chip.

from terminal, full output and backtrace attached:
i915_drm_batchbuffer.c:187:i915_drm_batchbuffer_flush: Assertion `ret == 0'
failed.


Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
OpenGL renderer string: Gallium 0.4 on i915 (chipset: 945G)
OpenGL version string: 2.0 Mesa 7.12-devel (git-99fbf7c)
Kernel: 3.1.6-1.fc16.i686
xf86-video-intel: 0dc5c0651cb691fb8811cdf3075b3d322f9d37f8 (with SNA enabled)
X.Org X Server 1.11.3
Firefox: 9.0.1

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.


More information about the dri-devel mailing list