[Bug 107586] New: i915 GPU HANG: ecode 9:0:0x85dffffb
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Aug 16 03:48:53 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=107586
Bug ID: 107586
Summary: i915 GPU HANG: ecode 9:0:0x85dffffb
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: ddv2005 at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 141129
--> https://bugs.freedesktop.org/attachment.cgi?id=141129&action=edit
drm crash dump
Hello,
I have video player app that works fine on i3-7100U and Atom z8350. The same
HDD image hangs on i5-7600 in 3 seconds. I tried all kernels 4.12-4.18 but the
same:
[ 42.723507] [drm] GPU HANG: ecode 9:0:0x85dffffb, in vplayer [1867], reason:
hang on rcs0, action: reset
[ 42.723508] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 42.723508] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 42.723508] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 42.723509] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 42.723509] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 42.723515] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[ 46.048174] asynchronous wait on fence i915:Xorg[1827]/0:41 timed out
I found that it hangs only if my app trying to download image from iGPU to
system memory via OpenGL Pixel Buffer Object. If I disable PBO and downloading
image without PBO then it works fine.
Best Regards,
Dmitry
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180816/2a4231ad/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list