Bug 101260 - [IGT] [BSW] igt/gem_exec_reloc subtests fail Test assertion failure function
Summary: [IGT] [BSW] igt/gem_exec_reloc subtests fail Test assertion failure function
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Humberto Israel Perez Rodriguez
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-31 21:21 UTC by Humberto Israel Perez Rodriguez
Modified: 2017-06-27 19:53 UTC (History)
1 user (show)

See Also:
i915 platform: BSW/CHT
i915 features: display/Other


Attachments
dmesg.log (91.87 KB, text/plain)
2017-05-31 21:21 UTC, Humberto Israel Perez Rodriguez
no flags Details
kern.log (10.60 KB, text/plain)
2017-05-31 21:22 UTC, Humberto Israel Perez Rodriguez
no flags Details

Description Humberto Israel Perez Rodriguez 2017-05-31 21:21:48 UTC
Created attachment 131621 [details]
dmesg.log

The following test cases fail on BSW with latest configuration

testlist
====================================
igt@gem_exec_reloc@readonly-29
igt@gem_exec_reloc@readonly-25
igt@gem_exec_reloc@readonly-20
igt@gem_exec_reloc@mmap-31
igt@gem_exec_reloc@wc-31
igt@gem_exec_reloc@readonly-28
igt@gem_exec_reloc@readonly-26
igt@gem_exec_reloc@readonly-27
igt@gem_exec_reloc@readonly-24
igt@gem_exec_reloc@readonly-22
igt@gem_exec_reloc@readonly-23
igt@gem_exec_reloc@readonly-21
igt@gem_exec_reloc@readonly-31
igt@gem_exec_reloc@readonly-16
igt@gem_exec_reloc@readonly-13
igt@gem_exec_reloc@readonly-18
igt@gem_exec_reloc@readonly-17
igt@gem_exec_reloc@readonly-15
igt@gem_exec_reloc@readonly-14
igt@gem_exec_reloc@readonly-12
igt@gem_exec_reloc@readonly-19
igt@gem_exec_reloc@readonly-30
igt@gem_exec_reloc@gtt-31
igt@gem_exec_reloc@cpu-31

test log
==============================================
IGT-Version: 1.18-g00ce341 (x86_64) (Linux: 4.12.0-rc3-drm-tip-ww22-commit-4aa1d46+ x86_64)
(gem_exec_reloc:1680) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_exec_reloc:1680) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_reloc:1680) drmtest-DEBUG: Test requirement passed: drmSetMaster(fd) == 0
(gem_exec_reloc:1680) drmtest-DEBUG: Test requirement passed: is_i915_device(fd) && has_known_intel_chipset(fd)
(gem_exec_reloc:1680) ioctl-wrappers-DEBUG: Test requirement passed: err == 0
(gem_exec_reloc:1680) ioctl-wrappers-DEBUG: Test requirement passed: has_ban_period || has_bannable
(gem_exec_reloc:1680) igt-gt-DEBUG: Test requirement passed: has_gpu_reset(fd)
(gem_exec_reloc:1680) igt-core-DEBUG: Starting subtest: readonly-27
(gem_exec_reloc:1680) intel-os-DEBUG: Checking 2 surfaces of size 134,217,728 bytes (total 268,439,552) against RAM
(gem_exec_reloc:1680) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_exec_reloc:1680) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_reloc:1680) intel-os-DEBUG: Test requirement passed: __intel_check_memory(count, size, mode, &required, &total)
(gem_exec_reloc:1680) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation()
(gem_exec_reloc:1680) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:624:
(gem_exec_reloc:1680) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0
(gem_exec_reloc:1680) ioctl-wrappers-CRITICAL: error: -14 != 0
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [gem_execbuf+0x44]
  #2 [from_mmap+0x174]
  #3 [__real_main651+0xbb8]
  #4 [main+0x33]
  #5 [__libc_start_main+0xf1]
  #6 [_start+0x29]
  #7 [<unknown>+0x29]
Subtest readonly-27 failed.
**** DEBUG ****
(gem_exec_reloc:1680) intel-os-DEBUG: Checking 2 surfaces of size 134,217,728 bytes (total 268,439,552) against RAM
(gem_exec_reloc:1680) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_exec_reloc:1680) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_reloc:1680) intel-os-DEBUG: Test requirement passed: __intel_check_memory(count, size, mode, &required, &total)
(gem_exec_reloc:1680) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation()
(gem_exec_reloc:1680) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:624:
(gem_exec_reloc:1680) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0
(gem_exec_reloc:1680) ioctl-wrappers-CRITICAL: error: -14 != 0
****  END  ****
Subtest readonly-27: FAIL (3.232s)
(gem_exec_reloc:1680) igt-core-DEBUG: Exiting with status code 99
(gem_exec_reloc:1680) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'

Software
======================================
kernel version              : 4.12.0-rc3-drm-tip-ww22-commit-4aa1d46+
architecture                : x86_64
os version                  : Ubuntu 16.10
os codename                 : yakkety
kernel driver               : i915
bios revision               : 0.33
bios release date           : 08/12/2015
ksc                         : 0.16


Graphic drivers
===================================================
Component: drm
    tag: libdrm-2.4.80-18-gce9e3ba
    commit: ce9e3ba6e2cc65e1e9e6e05a5f326c4dd25ab2c4

Component: cairo
    tag: 1.15.4-22-g0fd0fd0
    commit: 0fd0fd0ae9ad8cfb177bb844091de98c0235917e

Component: intel-gpu-tools
    tag: intel-gpu-tools-1.18-211-g00ce341
    commit: 00ce341b95c718611689ded8ccec45086186c5b7

Component: piglit
    tag: piglit-v1
    commit: ebbb9c5dcc6a637884d54e06eb430a8c14993413

kernel
===================================================
commit 4aa1d46d3b24bbe545cdf7cbd407c18f5cd5e43d
Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Wed May 31 10:59:05 2017 +0200
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Wed May 31 10:59:05 2017 +0200

    drm-tip: 2017y-05m-31d-08h-58m-36s UTC integration manifest
	
======================================
             Hardware
======================================
platform                   : BSW
motherboard model          : 10G9000NUS
motherboard id             : BRASWELL
form factor                : Desktop
manufacturer               : LENOVO
cpu family                 : Pentium
cpu family id              : 6
cpu information            : Intel(R) Pentium(R) CPU  N3700  @ 1.60GHz
gpu card                   : Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 21) (prog-if 00 [VGA controller])
memory ram                 : 7.68 GB
max memory ram             : 8 GB
cpu thread                 : 4
cpu core                   : 4
cpu model                  : 76
cpu stepping               : 3
socket                     : Socket BGA1155
signature                  : Type 0, Family 6, Model 76, Stepping 3
hard drive                 : 476GiB (512GB)
current cd clock frequency : 266667 kHz
maximum cd clock frequency : 320000 kHz
displays connected         : DP-1 DP-3


======================================
             kernel parameters
======================================
quiet drm.debug=0xe auto panic=1 nmi_watchdog=panic resume=/dev/sda3 fastboot

Attachments
=======================================
dmesg.log
kern.log
Comment 1 Humberto Israel Perez Rodriguez 2017-05-31 21:22:17 UTC
Created attachment 131622 [details]
kern.log
Comment 2 Chris Wilson 2017-06-16 16:19:19 UTC
commit 2889caa9232109afc8881f29a2205abeb5709d0c
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Jun 16 15:05:19 2017 +0100

    drm/i915: Eliminate lots of iterations over the execobjects arra
Comment 3 Elizabeth 2017-06-16 21:12:48 UTC
Could you please test this again to confirm is fixed. Thank you.
Comment 4 Humberto Israel Perez Rodriguez 2017-06-27 19:53:32 UTC
with the following kernel commit this issue is gone for BSW platform

commit 961848b8ac24a804b9c36d6ab243b788793ab406
Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Tue Jun 27 14:05:03 2017 +0200
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Tue Jun 27 14:05:03 2017 +0200

    drm-tip: 2017y-06m-27d-12h-04m-29s UTC integration manifest


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.