Bug 112321 - i915 GPU HANG: ecode 9:0:0x85ad939e, in Xorg [1736], reason: Hang on rcs0,
Summary: i915 GPU HANG: ecode 9:0:0x85ad939e, in Xorg [1736], reason: Hang on rcs0,
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-18 14:02 UTC by Vasan
Modified: 2019-11-29 19:48 UTC (History)
1 user (show)

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


Attachments
GPU crash dump (39.62 KB, text/plain)
2019-11-18 14:02 UTC, Vasan
no flags Details

Description Vasan 2019-11-18 14:02:07 UTC
Created attachment 145991 [details]
GPU crash dump

i am getting "GPU HANG: ecode 9:0:0x85ad939e, in Xorg [1736], reason: Hang on rcs0" error message in kernel log when i stream video  using Gstreamr  libs. attached GPU crash dump. any help is appreciated. 

Linux version 4.15.0-29-generic
i915 1.6.0
DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1)
Xorg server: 1.19.6
Comment 1 Chris Wilson 2019-11-18 14:11:11 UTC
* blinks

A real GPU hang:
  IPEHR: 0x7a726c61
looks more like pixel data than an instruction

4.15!

If your userspace stack is as old as the kernel; both require updates :)
Comment 2 Vasan 2019-11-19 05:28:49 UTC
Thanks for the reply. i will try to upgrade both the stack and the kernel and share the results. but i would like to know what is the root cause of this issue. is the problem occurs because of known bug in user stack or kernel driver? is there a way to trace what exactly gone wrong during the crash ?
Comment 3 Lakshmi 2019-11-20 08:13:49 UTC
(In reply to Vasan from comment #2)
> Thanks for the reply. i will try to upgrade both the stack and the kernel
> and share the results. but i would like to know what is the root cause of
> this issue. is the problem occurs because of known bug in user stack or
> kernel driver? is there a way to trace what exactly gone wrong during the
> crash ?

Unless we bisect the issue we can't know what is causing this issue. Anyway we always recommended to upgrade kernel to latest. Please try to reproduce with (https://cgit.freedesktop.org/drm-tip).
Comment 4 Martin Peres 2019-11-29 19:48:48 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/drm/intel/issues/618.


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.