[Bug 84719] New: Using maps.google.com in chromium crashes GPU (sandy bridge)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 6 07:23:26 PDT 2014


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

            Bug ID: 84719
           Summary: Using maps.google.com in chromium crashes GPU (sandy
                    bridge)
           Product: DRI
           Version: XOrg CVS
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: martin.blumenstingl+bfo at googlemail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 107429
  --> https://bugs.freedesktop.org/attachment.cgi?id=107429&action=edit
cat /sys/class/drm/card0/error

Using maps.google.com (zooming, dragging the map, etc.) crashes the GPU on my
i7-2600k.
This is reproducible (I need <5 min to reproduce it).

[18334.887908] [drm] stuck on render ring
[18334.888393] [drm] GPU HANG: ecode 0:0x85fffff8, in chromium [1950], reason:
Ring hung, action: reset
[18334.888394] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[18334.888395] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[18334.888395] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[18334.888396] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[18334.888397] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[18336.886927] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141006/633a9124/attachment.html>


More information about the intel-gfx-bugs mailing list