Bug 103503 - Intel i915 gpu hang on kernel 4.13.10
Summary: Intel i915 gpu hang on kernel 4.13.10
Status: CLOSED WORKSFORME
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-10-29 12:54 UTC by Štěpán Dalecký
Modified: 2018-04-25 08:21 UTC (History)
2 users (show)

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


Attachments
Gpu crash dump /sys/class/drm/card0/error (27.78 KB, text/x-log)
2017-10-29 12:54 UTC, Štěpán Dalecký
no flags Details

Description Štěpán Dalecký 2017-10-29 12:54:37 UTC
Created attachment 135153 [details]
Gpu crash dump /sys/class/drm/card0/error

[25019.852980] [drm] GPU HANG: ecode 9:1:0xfefffffe, reason: No progress on bcs0, action: reset
[25019.852981] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[25019.852982] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[25019.852982] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[25019.852982] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[25019.852983] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[25019.853020] drm/i915: Resetting chip after gpu hang
[25019.854795] [drm] RC6 off
Comment 1 Elizabeth 2017-10-31 21:43:48 UTC
This looks a bit like bug 101991:

  seqno: 0x000a4b79
  last_seqno: 0x000a4b7a
  waiting: yes
  ring->head: 0x000026c0
  ring->tail: 0x00002738
  hangcheck stall: no
  hangcheck action: active seqno
  hangcheck action timestamp: 4319687040, 3235335 ms ago
  ELSP[0]:  pid 24595, ban score 0, seqno        5:000a4b7a, emitted 3235339ms ago, head 000026c0, tail 00002740
  Active context: kwin_wayland[24595] user_handle 1 hw_id 5, ban score 0 guilty 0 active 0
Comment 2 Jani Saarinen 2018-03-29 07:10:25 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 3 Jani Saarinen 2018-04-25 08:21:47 UTC
Closing, please re-open is issue still exists.


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.