Bug 110867 - i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe, in chromium [3369], hang on rcs0
Summary: i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe, in chromium [3369], hang o...
Status: RESOLVED DUPLICATE of bug 111014
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-09 23:33 UTC by jshand2013
Modified: 2019-07-02 19:23 UTC (History)
2 users (show)

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

Attachments
card0 error dump (30.25 KB, text/plain)
2019-06-09 23:33 UTC, jshand2013 		Details
journalctl priority 7 (395.70 KB, text/plain)
2019-06-09 23:36 UTC, jshand2013 		Details
View All

Description jshand2013 2019-06-09 23:33:28 UTC 
Created attachment 144487 [details]
card0 error dump

[ 5382.083710] i915 0000:00:02.0: GPU HANG: ecode 7:1:0xfffffffe, in chromium [3369], hang on rcs0
[ 5382.083712] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 5382.083712] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 5382.083713] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 5382.083713] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 5382.083714] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 5382.083761] i915 0000:00:02.0: Resetting chip for hang on rcs0
Comment 1 jshand2013 2019-06-09 23:36:02 UTC 
Created attachment 144488 [details]
journalctl priority 7
Comment 2 Lakshmi 2019-06-10 12:06:05 UTC 
Changing the product considering this as a Mesa bug

rcs0 command stream:
  IDLE?: no
  START: 0x00409000
  HEAD:  0x9ac0faa0 [0x0000fa70]
    head = 0x0000faa0, wraps = 1238
  TAIL:  0x00010258 [0x0000fb30, 0x0000fb58]
  CTL:   0x0001f001
    len=131072, enabled
  MODE:  0x00004000
  HWS:   0x7fffe000
  ACTHD: 0x00000000 9ac0faa0
    at ring: 0x00000000
  IPEIR: 0x00000000
  IPEHR: 0x244f76b1
  INSTDONE: 0xfffffffe
  SC_INSTDONE: 0xffffffff
  SAMPLER_INSTDONE[0][0]: 0xffffffff
  ROW_INSTDONE[0][0]: 0xffffffff
  batch: [0x00000000_017ce000, 0x00000000_017cf000]
  BBADDR: 0x00000000_7fff29c4
  BB_STATE: 0x00000000
  INSTPS: 0x00000501
  INSTPM: 0x00000080
  FADDR: 0x00000000 00418aa0
  RC PSMI: 0x00000010
  FAULT_REG: 0x00000000
  SYNC_0: 0x00000000
  SYNC_1: 0x00000000
  GFX_MODE: 0x00002a00
  PP_DIR_BASE: 0x02ee0000
  seqno: 0x000b0e41
  last_seqno: 0x000b0e4a
  ring->head: 0x0000fa70
  ring->tail: 0x00010258
  hangcheck timestamp: 0ms (4296236248; epoch)
  engine reset count: 0
  Active context: chromium[3369] user_handle 12 hw_id 0, prio 0, ban score 0 guilty 0 active 0
Comment 3 Chris Wilson 2019-07-02 19:23:35 UTC 
Please test with

commit c84c9029d782a3a0d2a7f0522ecb907314d43e2c
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Apr 19 12:17:47 2019 +0100

    drm/i915/ringbuffer: EMIT_INVALIDATE *before* switch context

heading to v5.1 via stable in the next few weeks.

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

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.