Bug 89060 - [BSW SKL] igt/gem_ring_sync_loop causes GPU hang
Summary: [BSW SKL] igt/gem_ring_sync_loop causes GPU hang
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Mika Kahola
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-10 08:59 UTC by lu hua
Modified: 2015-11-26 16:19 UTC (History)
2 users (show)

See Also:
i915 platform: BSW/CHT, SKL
i915 features: GPU hang


Attachments
dmesg (124.87 KB, text/plain)
2015-02-10 08:59 UTC, lu hua
no flags Details
i915_error_state (2.79 MB, text/plain)
2015-02-10 09:04 UTC, lu hua
no flags Details

Description lu hua 2015-02-10 08:59:58 UTC
Created attachment 113305 [details]
dmesg

==System Environment==
--------------------------
Regression: not sure

no-working platforms: BSW

==kernel==
--------------------------
drm-intel-next-queued 21076372afe711072b9a447f22a098691dd0b2cb

==Bug detailed description==
-----------------------------
It causes GPU hang on BSW with drm-intel-next-queued kernel. On the drm-intel-nightly kernel, it has bug 88987, when bisect bug 88987, catch this issue.

output:
IGT-Version: 1.9-gbef692d (x86_64) (Linux: 3.19.0-rc5_kcloud_210763_20150209+ x86_64)

^C^C^C^C^C^C^C^C^C^C^C^C
real    12m41.468s
user    0m0.009s
sys     0m0.032s

==Reproduce steps==
---------------------------- 
1. ./gem_ring_sync_loop
Comment 1 lu hua 2015-02-10 09:04:05 UTC
Created attachment 113306 [details]
i915_error_state
Comment 2 ye.tian 2015-04-20 09:20:12 UTC
Tested it on the latest fixes kernel(39a880) and lgt (gbeddb3b), this issue still fails.

output:
-------------
root@x-bsw01:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time ./gem_ring_sync_loop      IGT-Version: 1.10-gbeddb3b (x86_64) (Linux: 4.0.0_drm-intel-fixes_39a880_20150414+ x86_64)
Test assertion failure function intel_batchbuffer_flush_on_ring, file intel_batchbuffer.     c:183:
Failed assertion: (drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0
Last errno: 5, Input/output error
Stack trace:
  #0 [__igt_fail_assert+0xf1]
  #1 [intel_batchbuffer_flush_on_ring+0xc5]
  #2 [main+0x19a]
  #3 [__libc_start_main+0xf5]
  #4 [_start+0x29]
  #5 [<unknown>+0x29]
Test gem_ring_sync_loop failed.
**** DEBUG ****
(gem_ring_sync_loop:4435) drmtest-DEBUG: Test requirement passed: fd >= 0
Test requirement passed: HAS_BLT_RING(intel_get_drm_devid(fd))
Test assertion failure function intel_batchbuffer_flush_on_ring, file intel_batchbuffer.     c:183:
Failed assertion: (drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0
Last errno: 5, Input/output error
****  END  ****
FAIL (11.640s)

real    0m17.722s
user    0m0.247s
sys     0m1.099s
Comment 3 Humberto Israel Perez Rodriguez 2015-09-23 17:29:26 UTC
still happen on SKL-Y with the latest kernel :

Kernel commit log:
commit b4c4542ba1abfb0d3d6913504502573bf2c62b12
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Aug 28 15:51:30 2015 +0200
drm-intel-nightly: 2015y-08m-28d-13h-50m-34s UTC integration manifest
Comment 4 cprigent 2015-10-01 16:53:35 UTC
Bug scrub: Assigned to Mika.
Comment 5 Rami 2015-10-02 15:38:30 UTC
Not reproduced on BSW with 4.3.0-rc2-drm-intel-nightly+
Hardware:
=========

Platform: Braswell M 
CPU : Intel(R) Celeron N3060 1.60GHz @ 1.6 GHz (family: 6, model: 76 stepping:
4)
SoC : BSW D0
QDF : K6XC
CRB : BRASWELL RVP Fab2
Mandatory Reworks : All 
Feature Reworks: F28, F32,F33 & F37
Optional reworks : O-01a


Software :
Linux distribution: Ubuntu 14.04 LTS 64 bits 
BIOS : BRAS.X64.B084.R00.1508310642
TXE FW : 2.0.0.2073
Ksc : 1.08

kernel 4.3.0-rc2-drm-intel-nightly+
commit 794e1cdfb84be003dbd287c69501c98ec280a89b
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Mon Sep 28 17:28:29 2015 +0300

    drm-intel-nightly: 2015y-09m-28d-14h-28m-11s UTC integration manifest

cairo: (HEAD, tag: 1.14.2) 93422b3cb5e0ef8104b8194c8873124ce2f5ea2d from
git://git.freedesktop.org/git/cairo
drm: (HEAD, tag: libdrm-2.4.64, tag: 2.4.64)
ab2fadabde3829b1ec56bd4756165dd9bd281488 from
git://git.freedesktop.org/git/mesa/drm
intel-driver: (HEAD, origin/master, origin/HEAD, master)
2a72f99d24714f2a58f400ef63b913d4cf9080b3 from
git://git.freedesktop.org/git/vaapi/intel-driver
libva: (HEAD, tag: libva-1.6.1, origin/v1.6-branch)
613eb962b45fbbd1526d751e88e0d8897af6c0e0 from
git://git.freedesktop.org/git/vaapi/libva
mesa: (HEAD, tag: mesa-10.6.7) 32efdc87cbf89cfe08ad9571cd756e27c803caa8 from
git://git.freedesktop.org/git/mesa/mesa
xf86-video-intel: (HEAD, origin/master, origin/HEAD, master)
f0fd4d500de03c30c7ce19915f85acadd1ca4e5d from
git://git.freedesktop.org/git/xorg/driver/xf86-video-intel
xserver: (HEAD, tag: xorg-server-1.17.2)
2123f7682d522619f101b05fb75efa75dabbe371 from
git://git.freedesktop.org/git/xorg/xserver

intel-gpu-tools: (HEAD, tag: intel-gpu-tools-1.12)
1f9e0550455be4b219954a026407dd23ec21b299 from
git://git.freedesktop.org/git/xorg/app/intel-gpu-tools

Result:
=======
./gem_ring_sync_loop
IGT-Version: 1.12-g1f9e055 (x86_64) (Linux: 4.3.0-rc2-drm-intel-nightly+ x86_64)
SUCCESS (63.582s)
Comment 6 Mika Kahola 2015-10-14 07:08:28 UTC
If this is not reproducible with the latest -nightly can we close this one?
Comment 7 cprigent 2015-11-26 16:18:51 UTC
Result is Pass on BSW-M and SKL-Y.

Platform: Braswell M
CPU : Intel(R) Celeron N3060 1.60GHz @ 1.6 GHz (family: 6, model: 76 stepping:
4)
SoC : BSW D0
QDF : K6XC
CRB : BRASWELL RVP Fab2
Mandatory Reworks : All 
Feature Reworks: F28, F32, F33, F35, F37
Optional reworks : O-01a; O-02, O-03
Software 
BIOS : BRAS.X64.B088.R00.1510270350
TXE FW : 2.0.0.2093
Ksc : 1.08
Linux : Ubuntu 15.04 64 bits
BIOS : SKLSE2R1.R00.B104.B01.1511110114
ME FW : 11.0.0.1191
Ksc (EC FW): 1.20
Kernel 4.4.0-rc2 nighlty 9e096bc from git://anongit.freedesktop.org/drm-intel
  commit 9e096bc5a20d1d8122740136ab6c584afd4cb913
  Author: Imre Deak <imre.deak@intel.com>
  Date:   Mon Nov 23 17:11:06 2015 +0200
  drm-intel-nightly: 2015y-11m-23d-15h-10m-47s UTC integration manifest
Mesa 11.0.5 from http://cgit.freedesktop.org/mesa/mesa/
xf86-video-intel - 2.99.917 from
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/
Libdrm - 2.4.65 from http://cgit.freedesktop.org/mesa/drm/
Libva - 1.6.1 from http://cgit.freedesktop.org/libva/
vaapi intel-driver - 1.6.1 from http://cgit.freedesktop.org/vaapi/intel-driver
Cairo - 1.14.2 from http://cgit.freedesktop.org/cairo
Xorg Xserver - 1.17.2 from http://cgit.freedesktop.org/xorg/xserver
IGT 1.12 gd84e624 from http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/

Hardware
Platform: SKY LAKE Y A0 QUAL
CPU : Intel(R) Core(TM) M5-6Y54 @ 1.10GHz 4MB (family: 6, model: 78  stepping: 3)
MCP : SKL-Y  D1  
QDF : QJ9W
CPU : SKL D0
Chipset PCH: Sunrise Point LP C1       
CRB : SKY LAKE Y LPDDR3 RVP3 CRB FAB2
Reworks : All Mandatories + FBS02 & FBS03, O-06
Software 
Linux : Ubuntu 14.04 64 bits
BIOS : SKLSE2R1.R00.B104.B01.1511110114
ME FW : 11.0.0.1191
Ksc (EC FW): 1.20
Kernel 4.4.0-rc2 nighlty 7a06d77 from git://anongit.freedesktop.org/drm-intel
  commit 7a06d7743ef3ffa5b93bd4e528909834da8d92b6
  Author: Daniel Vetter <daniel.vetter@ffwll.ch>
  Date:   Wed Nov 25 18:09:23 2015 +0100
  drm-intel-nightly: 2015y-11m-25d-17h-08m-45s UTC integration manifest
  With patch https://bugs.freedesktop.org/attachment.cgi?id=119736 applied
Mesa 11.0.5 from http://cgit.freedesktop.org/mesa/mesa/
xf86-video-intel - 2.99.917 from http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/
Libdrm - 2.4.65 from http://cgit.freedesktop.org/mesa/drm/
Libva - 1.6.1 from http://cgit.freedesktop.org/libva/
vaapi intel-driver - 1.6.1 from http://cgit.freedesktop.org/vaapi/intel-driver
Cairo - 1.14.2 from http://cgit.freedesktop.org/cairo
Xorg Xserver - 1.17.2 from http://cgit.freedesktop.org/xorg/xserver
DMC 1.23 and GuC 4.3 from https://01.org/linuxgraphics/intel-linux-graphics-firmwares
IGT 1.12-gd84e624 from http://cgit.freedesktop.org/xorg/app/intel-gpu-tools/
Monitor: Asus PB287Q connected without any video adaptation
Comment 8 cprigent 2015-11-26 16:19:19 UTC
So closed


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.