Bug 84906 - [SNB uxa] GPU Hang stuck on render ring (3.13)
Summary: [SNB uxa] GPU Hang stuck on render ring (3.13)
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-11 10:11 UTC by Sergei
Modified: 2017-07-24 22:51 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (24.58 KB, text/plain)
2014-10-11 10:11 UTC, Sergei
no flags Details
contains /sys/class/drm/card0/error (654.16 KB, application/zip)
2014-10-11 17:45 UTC, Sergei
no flags Details

Description Sergei 2014-10-11 10:11:45 UTC
Created attachment 107707 [details]
Xorg.0.log

Oct 11 11:26:27 nuc1 kernel: [ 3133.897754] perf samples too long (2515 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
Oct 11 11:27:18 nuc1 kernel: [ 3184.433690] [drm] stuck on render ring
Oct 11 11:27:18 nuc1 kernel: [ 3184.433715] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Oct 11 11:27:18 nuc1 kernel: [ 3184.433718] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Oct 11 11:27:18 nuc1 kernel: [ 3184.433721] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Oct 11 11:27:18 nuc1 kernel: [ 3184.433724] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Oct 11 11:27:18 nuc1 kernel: [ 3184.433727] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Oct 11 11:28:14 nuc1 kernel: [ 3240.426771] [drm] stuck on render ring
Oct 11 11:39:01 nuc1 CRON[13859]: (root) CMD (  [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime))
Oct 11 11:41:48 nuc1 kernel: [ 4054.326400] [drm] stuck on render ring
Oct 11 11:45:24 nuc1 kernel: [ 4270.299767] [drm] stuck on render ring


The file /sys/class/drm/card0/error contains just

no error state collected

(please instruct how to collect one)


# lspci -v

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) (prog-if 00 [VGA controller])
	Subsystem: Intel Corporation Device 2044
	Flags: bus master, fast devsel, latency 0, IRQ 43
	Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
	Memory at e0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=64]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [a4] PCI Advanced Features
	Kernel driver in use: i915
Comment 1 Chris Wilson 2014-10-11 15:25:58 UTC
You need to grab the /sys/class/drm/card0/error after the error occurs and before rebotting.
Comment 2 Sergei 2014-10-11 17:45:35 UTC
Created attachment 107723 [details]
contains /sys/class/drm/card0/error

the file err.zip contains /sys/class/drm/card0/error copied after the systems hangs, before reboot (obtained using ssh from a remote system)
Comment 3 Paulo Zanoni 2014-10-13 18:05:52 UTC
You're running Kernel 3.13, which is quite old for development purposes. Can you please check whether this problem still happens on newer Kernels?

You could try downloading a newer Kernel from your distro's development version, or maybe you could try testing the drm-intel-nightly branch from http://cgit.freedesktop.org/drm-intel/log/?h=drm-intel-nightly .
Comment 4 Chris Wilson 2014-12-21 21:00:49 UTC
Also the hang is in an UXA batch buffer, you could also try xf86-video-intel-2.99.917.
Comment 5 Ander Conselvan de Oliveira 2015-06-04 19:32:34 UTC
Closing due to inactivity. Please reopen if you are able to provide the requested information.


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.