Bug 105815

Summary:	[cfl] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg
Product:	Mesa	Reporter:	dr.riza
Component:	Drivers/DRI/i965	Assignee:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Status:	RESOLVED MOVED	QA Contact:	Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity:	major
Priority:	medium	CC:	dr.riza, intel-gfx-bugs
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	GPU crash dump

Description dr.riza 2018-03-30 06:59:50 UTC

Created attachment 138441 [details]
GPU crash dump

This GPU crash happened when I opened a new project in the IDEA IntelliJ application (https://www.jetbrains.com/idea/) which runs as a java process.

Java version on this machine:

ava(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)

Here's the output of dmesg just before the crash
-------------------------------------------------

Mar 30 07:34:08 xxx.xxx.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hostn
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] GPU HANG: ecode 9:0:0x84dfbffc, in Xorg [2225], reason: Hang on rcs0, action: reset
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Mar 30 07:34:34 xxx.xxx.com kernel: [drm] GPU crash dump saved to /sys/class/drm/card1/error


Please find attached the crash report.

Comment 1 dr.riza 2018-03-30 07:01:19 UTC

cat /etc/redhat-release 

Fedora release 27 (Twenty Seven)

uname -a

Linux xxx.xxx.com 4.15.10-300.fc27.x86_64 #1 SMP Thu Mar 15 17:13:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Comment 2 Kenneth Graunke 2018-03-30 18:32:31 UTC

What version of Mesa are you using?

Comment 3 dr.riza 2018-03-31 11:17:06 UTC

glxinfo | grep Open

    Vendor: Intel Open Source Technology Center (0x8086)
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Coffeelake 3x8 GT2) 
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.6
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 17.3.6
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 17.3.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

Comment 4 Lionel Landwerlin 2018-04-01 23:56:49 UTC

Looks like a hang triggered by the X driver.

Comment 5 GitLab Migration User 2019-09-25 19:10:25 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/mesa/mesa/issues/1710.

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.