Created attachment 125031 [details] dmesg
Created attachment 125032 [details] GPU crash dump
Mikhail, this sounds like you have a previous segfault in your Chrome caused by xfs (not on graphics / i915 side) even if finally there was some gpu hang reported after (but still linked to Chrome). - Can you confirm whether or not this Chrome crash, you launch again Chrome or Chrome respawn by itself? - If Chrome is not getting this segfault with xfs, I think that you are not getting that gpu hang?
Segfault in Chrome not related to xfs, this occured in different time. '*ERROR* Hangcheck timer elapsed' occured when I try open too much tabs in chrome and seems chrome segfault same reason. The mouse cursor freezes for a while, and after this error entry appear in dmesg log.
Created attachment 125563 [details] dmesg
Created attachment 125564 [details] GPU crash dump
commit 83348ba84ee0d5d4d982e5382bfbc8b2a2d05e75 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Aug 9 17:47:51 2016 +0100 drm/i915: Move missed interrupt detection from hangcheck to breadcrumbs In commit 2529d57050af ("drm/i915: Drop racy markup of missed-irqs from idle-worker") the racy detection of missed interrupts was removed when we went idle. This however opened up the issue that the stuck waiters were not being reported, causing a test case failure. If we move the stuck waiter detection out of hangcheck and into the breadcrumb mechanims (i.e. the waiter) itself, we can avoid this issue entirely. This leaves hangcheck looking for a stuck GPU (inspecting for request advancement and HEAD motion), and breadcrumbs looking for a stuck waiter - hopefully make both easier to understand by their segregation.
*** Bug 96887 has been marked as a duplicate of this bug. ***
*** Bug 95361 has been marked as a duplicate of this bug. ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.