Bug 98477

Summary:

[BDW][Regression] gem_exec_flush subtests failing due to assertion failures

Product:

DRI

Reporter:

Jairo Miramontes <jairo.daniel.miramontes.caton>

Component:

DRM/Intel

Assignee:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Status:

CLOSED WONTFIX

QA Contact:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Severity:

normal

Priority:

medium

CC:

intel-gfx-bugs

Version:

DRI git

Keywords:

regression

Hardware:

Other

OS:

All

Whiteboard:

i915 platform:

BDW

i915 features:

GEM/execlists

Attachments:

Description	Flags
dmesg log BSW when eexecuting both gem_exec_flush tests	none

Description Jairo Miramontes 2016-10-28 17:05:28 UTC

Created attachment 127589 [details]
dmesg log BSW when eexecuting both gem_exec_flush tests

The following tests regressions were found using the below Kernel configuration.

gem_exec_flush@uc-ro-before-blt-interruptible	
gem_exec_flush@uc-rw-before-blt-interruptible

Attached dmesg.log files


Kernel
==========================================================================
commit 17dc529acb9a6a4328b419048e32df586b90646b
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Oct 24 14:24:26 2016 +0100

    drm-intel-nightly: 2016y-10m-24d-13h-22m-52s UTC integration manifest



Stack
=========================================================================
Component         : drm
	url       : http://cgit.freedesktop.org/mesa/drm
	tag       : libdrm-2.4.71-6-g9e24d0c
	commit    : 9e24d0c

Component         : cairo
	url       : http://cgit.freedesktop.org/cairo
	tag       : 1.15.2
	commit    : db8a7f1



This tests were passing using the following Kernel:

        Kernel   : drm-intel-nightly WW42
	version  : 4.8.0
	commit   : 15dfed2

Comment 1 Chris Wilson 2016-10-28 17:26:21 UTC

These are expected to fail occasionally due to speculative execution. Without the logs I presume we are hitting this hw feature the test is designed to detect (although imperfectly).

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.