<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GPU crash - segfault at error in chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=88739#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GPU crash - segfault at error in chrome" href="https://bugs.freedesktop.org/show_bug.cgi?id=88739">bug 88739</a> from <a class="email" href="mailto:vstadnichenko@gmail.com" title="Victor <vstadnichenko@gmail.com>"> Victor</a> <pre>(In reply to Victor from <a href="show_bug.cgi?id=88739#c0">comment #0</a>) > Every time 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 LM17.1 Rebecca 32 Mate, Core2Duo <a href="mailto:6420@2.13GHz">6420@2.13GHz</a>, P5B-MX/WIFI-AP, 2GiB RAM, 1Tb SATA Ext4, 10Gib root, 2GiB swap, Logitech Mx-400 mouse</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>