Bug 103042 - hang from chrome: GPU HANG: ecode 9:0:0x84df7cfc, in chrome [19997], reason: Hang on rcs0, action: reset
Summary: hang from chrome: GPU HANG: ecode 9:0:0x84df7cfc, in chrome [19997], reason: ...
Status: CLOSED DUPLICATE of bug 103076
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-29 23:18 UTC by Jan Kundrát
Modified: 2017-10-03 22:09 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: GPU hang


Attachments
/sys/class/drm/card0/error (131.02 KB, text/plain)
2017-09-29 23:18 UTC, Jan Kundrát
no flags Details

Description Jan Kundrát 2017-09-29 23:18:18 UTC
Created attachment 134573 [details]
/sys/class/drm/card0/error

Playing a video in mpv and playing an OpenGL game via Chrome, I got:

[27961.378637] [drm] GPU HANG: ecode 9:0:0x84df7cfc, in chrome [19997], reason: Hang on rcs0, action: reset
[27961.378639] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[27961.378639] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[27961.378640] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[27961.378641] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[27961.378641] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[27961.378695] drm/i915: Resetting chip after gpu hang
[27961.379015] [drm] RC6 on
[27975.346141] drm/i915: Resetting chip after gpu hang
[27975.346491] [drm] RC6 on
[27975.348518] usb 2-4.1.3.3: reset SuperSpeed USB device number 13 using xhci_hcd
[27975.445216] usb 2-4.1.3.3: USB disconnect, device number 13
[27975.472746] usb 2-4.1.3: Disable of device-initiated U1 failed.
[27975.476352] usb 2-4.1.3: Disable of device-initiated U2 failed.
[27975.766212] usb 2-4.1.3: reset SuperSpeed USB device number 8 using xhci_hcd
[27976.050646] usb 2-4.1.3.3: new SuperSpeed USB device number 14 using xhci_hcd
[27976.160991] usb 2-4.1.3.3: New USB device found, idVendor=0bda, idProduct=0307
[27976.160998] usb 2-4.1.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27976.161002] usb 2-4.1.3.3: Product: USB3.0 Card Reader
[27976.161005] usb 2-4.1.3.3: Manufacturer: Realtek
[27976.161009] usb 2-4.1.3.3: SerialNumber: 201006010301
[27976.170757] usb-storage 2-4.1.3.3:1.0: USB Mass Storage device detected
[27976.172005] scsi host0: usb-storage 2-4.1.3.3:1.0
[27977.209134] scsi 0:0:0:0: Direct-Access     Generic- SD/MMC/MS/MSPRO  1.00 PQ: 0 ANSI: 6
[27977.210043] sd 0:0:0:0: Attached scsi generic sg0 type 0
[27977.215948] sd 0:0:0:0: [sda] Attached SCSI removable disk
[27987.314457] drm/i915: Resetting chip after gpu hang
[27987.314775] [drm] RC6 on
[27989.620985] usb 2-4.1.3.3: reset SuperSpeed USB device number 14 using xhci_hcd
[27999.346723] drm/i915: Resetting chip after gpu hang
[27999.347092] [drm] RC6 on
[27999.656223] usb 2-4.1.3.3: reset SuperSpeed USB device number 14 using xhci_hcd
[28007.346872] drm/i915: Resetting chip after gpu hang
[28007.347211] [drm] RC6 on

Attached is my /sys/class/drm/card0/error .

dmesg is telling me to file a new bug even though https://bugs.freedesktop.org/show_bug.cgi?id=102629 looks pretty much related.

kernel 4.13.2
Google Chrome 62.0.3198.0
mesa 17.2.1
Comment 1 Elizabeth 2017-10-02 19:21:15 UTC
This seems to be related https://bugs.freedesktop.org/show_bug.cgi?id=101991#c3
Comment 2 Chris Wilson 2017-10-03 13:15:59 UTC

*** This bug has been marked as a duplicate of bug 103076 ***


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.