Bug 101533

Summary: [SKL] drm/i915: Resetting chip after gpu hang with webgl
Product: Mesa Reporter: Joel <joel.stan>
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED MOVED QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs, voineavladimir
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: /sys/class/drm/card0/error

Description Joel 2017-06-21 08:30:46 UTC
Created attachment 132110 [details]
/sys/class/drm/card0/error

Running Ubuntu's 4.11.0-6-generic kernel, whenever Facebook loads a webGL widget in Google Chrome my screen locks up for a few seconds. When it comes back, Chrome reports that webGL has crashed and I see this in the kernel log:

[121807.432832] drm/i915: Resetting chip after gpu hang
[121807.433343] [drm] RC6 on
[121807.448255] [drm] GuC firmware load skipped
[121819.496336] drm/i915: Resetting chip after gpu hang
[121819.496482] [drm] RC6 on
[121819.516308] [drm] GuC firmware load skipped

I've attached the contents of /sys/class/drm/card0/error.

i915 bits from boot up:

i915 0000:00:02.0: enabling device (0006 -> 0007)
[drm] Finished loading DMC firmware i915/skl_dmc_ver1_26.bin (v1.26)
i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=mem
[drm] Initialized i915 1.6.0 20170123 for 0000:00:02.0 on minor 0
[drm] Initialized i915 1.6.0 20170123 for 0000:00:02.0 on minor 0
i915 0000:00:02.0: fb0: inteldrmfb frame buffer device

The machine is a 4th gen X1 carbon, running Lenovo's N1FET50W (1.24) firmware.
Comment 1 Elizabeth 2018-03-06 22:03:42 UTC
Hi Joel, is this still reproducible? Which mesa version are you using?
Comment 2 GitLab Migration User 2019-09-25 19:02:50 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1603.

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.