Bug 100188

Summary: GPU HANG: ecode 9:0:0x84dffff8, in Xorg [2052], reason: Hang on render ring, action: reset
Product: DRI Reporter: peterwwillis
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
crash error log
none
Xorg log file none

Description peterwwillis 2017-03-13 20:17:01 UTC
Created attachment 130204 [details]
crash error log

The following is a bug report of a crash found in my kernel dmesg logs.

It's apparently a crash for the onboard Intel graphics on my laptop (Lenovo IdeaPad 510S-14ISK, MFR# 80TK002GUS), but this laptop also has a Radeon graphics card which should be driving the screen, so I do not know why this crashed. Also attached is my Xorg log file.

Below is the kernel message log that prompted the crash. Attached is the crash output.

--

[  868.226820] [drm] PCIE GART of 3909M enabled (table at 0x0000000000040000).
[  868.229441] cant't get the mac of 5 
[  868.237757] [drm] ring test on 0 succeeded in 9 usecs
[  868.237935] [drm] ring test on 1 succeeded in 13 usecs
[  868.237953] [drm] ring test on 2 succeeded in 9 usecs
[  868.237958] [drm] ring test on 3 succeeded in 2 usecs
[  868.237962] [drm] ring test on 4 succeeded in 1 usecs
[  868.237967] [drm] ring test on 5 succeeded in 2 usecs
[  868.237970] [drm] ring test on 6 succeeded in 1 usecs
[  868.237973] [drm] ring test on 7 succeeded in 1 usecs
[  868.237977] [drm] ring test on 8 succeeded in 1 usecs
[  868.238008] [drm] ring test on 9 succeeded in 4 usecs
[  868.238012] [drm] ring test on 10 succeeded in 3 usecs
[  873.967524] VI should always have 2 performance levels
[  874.549953] amdgpu 0000:01:00.0: GPU pci config reset
[  878.730658] [drm] PCIE GART of 3909M enabled (table at 0x0000000000040000).
[  878.733235] cant't get the mac of 5 
[  878.741569] [drm] ring test on 0 succeeded in 9 usecs
[  878.741748] [drm] ring test on 1 succeeded in 13 usecs
[  878.741767] [drm] ring test on 2 succeeded in 9 usecs
[  878.741772] [drm] ring test on 3 succeeded in 2 usecs
[  878.741775] [drm] ring test on 4 succeeded in 1 usecs
[  878.741778] [drm] ring test on 5 succeeded in 1 usecs
[  878.741784] [drm] ring test on 6 succeeded in 2 usecs
[  878.741787] [drm] ring test on 7 succeeded in 1 usecs
[  878.741790] [drm] ring test on 8 succeeded in 1 usecs
[  878.741821] [drm] ring test on 9 succeeded in 4 usecs
[  878.741825] [drm] ring test on 10 succeeded in 3 usecs
[  884.722628] VI should always have 2 performance levels
[  885.540882] amdgpu 0000:01:00.0: GPU pci config reset
[ 1247.004486] TCP: wlan0: Driver has suspect GRO implementation, TCP performance may be compromised.
[ 1288.751424] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [2052], reason: Hang on render ring, action: reset
[ 1288.751428] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1288.751429] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1288.751430] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1288.751431] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1288.751434] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1288.751493] drm/i915: Resetting chip after gpu hang
[ 1288.751560] [drm] RC6 on
[ 1288.767265] [drm] GuC firmware load skipped
[ 1289.243317] [drm] PCIE GART of 3909M enabled (table at 0x0000000000040000).
[ 1289.246154] cant't get the mac of 5
Comment 1 peterwwillis 2017-03-13 20:17:29 UTC
Created attachment 130205 [details]
Xorg log file
Comment 2 peterwwillis 2017-03-13 20:26:23 UTC
From other similar bugs it looks like these aren't getting looked at, but in case it matters this is with the 2016-12-11 git kernel firmware installed, Slackware 14.2 64bit with all updated packages as of this writing, with the exception of a kernel update to 4.9.13 using slack's 'huge' kernel config as a base.
Comment 3 Chris Wilson 2017-03-13 20:47:17 UTC

*** This bug has been marked as a duplicate of bug 98999 ***

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.