Bug 93232 - GPU HANG: ecode 8:2:0x0000000a, in X [5392], reason: Ring hung, action: reset
Summary: GPU HANG: ecode 8:2:0x0000000a, in X [5392], reason: Ring hung, action: reset
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
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: 2015-12-03 16:49 UTC by mauro
Modified: 2016-09-20 16:00 UTC (History)
1 user (show)

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


Attachments
error (350.85 KB, text/plain)
2015-12-03 16:49 UTC, mauro
no flags Details
dmesg (74.62 KB, text/plain)
2015-12-03 16:50 UTC, mauro
no flags Details
Xorg.0.log (40.22 KB, text/plain)
2015-12-04 16:34 UTC, mauro
no flags Details

Description mauro 2015-12-03 16:49:29 UTC
Created attachment 120308 [details]
error

Reporting here as per dmesg instructions.
Error happens at boot time (100% reproducible).
HW is an ASUS f555 laptop with hybrid intel/AMD graphics (muxless), same as per similar (same?) error already reported in bug #92326 (but with newer sw).

mauro@pedro ~ $ uname -a
Linux pedro 4.2.6-nrj-laptop-1rosa-x86_64 #1 SMP PREEMPT Sun Nov 22 17:54:44 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
mauro@pedro ~ $ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars LE [Radeon HD 8530M / R5 M240] (rev ff)

libdrm version is 2.4.64
Comment 1 mauro 2015-12-03 16:50:05 UTC
Created attachment 120309 [details]
dmesg
Comment 2 Chris Wilson 2015-12-04 09:49:36 UTC
This batch is corrupt and unterminated:

blitter ring (submitted by X [5392]) --- gtt_offset = 0x00828000
00000000 :  54f00806
00000004 :  03cc0580
00000008 :  00000000
0000000c :  03000556
00000010 :  00000000
00000014 :  00000000
00000018 :  00001580
0000001c :  00420000
00000020 :  00000000
00000024 :  00000000
00000028 :  00000000
0000002c :  00000000
00000030 :  00000000

which is a strange mixture of new length with old relocation offsets. Please attach your Xorg.0.log.
Comment 3 mauro 2015-12-04 16:34:11 UTC
Created attachment 120353 [details]
Xorg.0.log

Here it is
Comment 4 yann 2016-09-20 14:48:52 UTC
There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.
Comment 5 mauro 2016-09-20 15:59:01 UTC
I'm now running kernel 4.6.2 and I'm not seeing this error any more.
Comment 6 yann 2016-09-20 16:00:14 UTC
(In reply to mauro from comment #5)
> I'm now running kernel 4.6.2 and I'm not seeing this error any more.

Thanks Mauro!


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.