[Bug 88739] New: GPU crash - segfault at error in chrome

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jan 23 01:49:32 PST 2015


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

            Bug ID: 88739
           Summary: GPU crash - segfault at error in chrome
           Product: DRI
           Version: XOrg git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: vstadnichenko at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

It looks like when I open a page that contains video content in Google Chrome,
the page stops responding, then the cursor becomes stalled and stays at that
location, while the mouse keeps working moving the focus point instead of the
cursor. The focus point highlights the items it's pointing to, and the mouse
operates normally while the cursor is lost behind.

If I log off, the login page is corrupted - it's 2-3 inches horizontally offset
to the side.

syslog:
Jan 23 12:18:30 sanmateo kernel: [  172.035296] Watchdog[2768]: segfault at 0
ip b611130f sp afb58cc0 error 6 in chrome[b20b2000+5689000]
Jan 23 12:18:43 sanmateo kernel: [  185.122790] Watchdog[3067]: segfault at 0
ip b61b130f sp afbf8cc0 error 6 in chrome[b2152000+5689000]
Jan 23 12:18:56 sanmateo kernel: [  197.528221] Watchdog[3075]: segfault at 0
ip b60fd30f sp afb44cc0 error 6 in chrome[b209e000+5689000]
Jan 23 12:19:00 sanmateo kernel: [  201.816014] [drm] stuck on render ring
Jan 23 12:19:00 sanmateo kernel: [  201.816022] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Jan 23 12:19:00 sanmateo kernel: [  201.816024] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
Jan 23 12:19:00 sanmateo kernel: [  201.816026] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
Jan 23 12:19:00 sanmateo kernel: [  201.816029] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
Jan 23 12:19:00 sanmateo kernel: [  201.816031] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
Jan 23 12:19:00 sanmateo kernel: [  201.818106] [drm:i915_set_reset_status]
*ERROR* render ring hung inside bo (0x4697000 ctx 0) at 0x4698a04
Jan 23 12:19:00 sanmateo kernel: [  201.984019] [drm] GMBUS [i915 gmbus vga]
timed out, falling back to bit banging on pin 2
Jan 23 12:19:00 sanmateo kernel: [  202.368018] [drm:i915_reset] *ERROR* Failed
to reset chip.

/sys/class/drm/card0/error: no error state collected

-- 
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/20150123/9181d8bc/attachment.html>


More information about the intel-gfx-bugs mailing list