Bug 102589 - [IGT][SKL] gem_exec_nop@headless Test assertion failure function headless
Summary: [IGT][SKL] gem_exec_nop@headless Test assertion failure function headless
Status: CLOSED DUPLICATE of bug 100572
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
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: 2017-09-07 15:15 UTC by Hector Velazquez
Modified: 2017-09-07 20:16 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Output log (9.41 KB, text/plain)
2017-09-07 15:15 UTC, Hector Velazquez
no flags Details
Dmesg log (43.85 KB, text/plain)
2017-09-07 15:16 UTC, Hector Velazquez
no flags Details

Description Hector Velazquez 2017-09-07 15:15:36 UTC
Created attachment 134045 [details]
Output log

The following tests Fail on SKL 

Tests List:

igt@gem_exec_nop@headless


======================================
        Output Sample
======================================
...
(gem_exec_nop:2919) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_nop:2919) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
Without a display connected (headless): 18.94us
(gem_exec_nop:2919) CRITICAL: Test assertion failure function headless, file gem_exec_nop.c:185:
(gem_exec_nop:2919) CRITICAL: Failed assertion: (n_headless) <= (1.0 + 0.1f) * n_display && (n_headless) >= (1.0 - 0.1f) * n_display
(gem_exec_nop:2919) CRITICAL: 'n_headless' != 'n_display' (0.000019 not within 10.000000% tolerance of 0.000004)
Subtest headless failed.
**** DEBUG ****
(gem_exec_nop:2919) DEBUG: Test requirement passed: nr_connected > 0
(gem_exec_nop:2919) igt-kms-DEBUG: VT: graphics mode set (mode was 0x0)
(gem_exec_nop:2919) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
...

...
(gem_exec_nop:2919) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_nop:2919) INFO: Without a display connected (headless): 18.94us
(gem_exec_nop:2919) CRITICAL: Test assertion failure function headless, file gem_exec_nop.c:185:
(gem_exec_nop:2919) CRITICAL: Failed assertion: (n_headless) <= (1.0 + 0.1f) * n_display && (n_headless) >= (1.0 - 0.1f) * n_display
(gem_exec_nop:2919) CRITICAL: 'n_headless' != 'n_display' (0.000019 not within 10.000000% tolerance of 0.000004)
(gem_exec_nop:2919) igt-core-INFO: Stack trace:
(gem_exec_nop:2919) igt-core-INFO:   #0 [__igt_fail_assert+0x101]
(gem_exec_nop:2919) igt-core-INFO:   #1 [__real_main614+0x78d]
(gem_exec_nop:2919) igt-core-INFO:   #2 [__libc_csu_init+0x0]
****  END  ****
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [__real_main614+0x78d]
  #2 [__libc_csu_init+0x0]
Subtest headless: FAIL (10.760s)
(gem_exec_nop:2919) igt-core-DEBUG: Exiting with status code 99
(gem_exec_nop:2919) igt-kms-DEBUG: VT: original mode 0x0 restored
...

This is my configuration:

======================================
        Graphic stack
======================================

Component: drm
    tag: libdrm-2.4.81-53-gd55d080
    commit: d55d0804f9e37637d7510f38f97e07a50c6b7baa

Component: cairo
    tag: 1.15.6-30-gc29db4f
    commit: c29db4f0de52727406a8b62f4da9a382084b5a79

Component: intel-gpu-tools
    tag: intel-gpu-tools-1.19-244-g4a1c8da
    commit: 4a1c8daff2005e2cbfe980d63bc0a0fb09cb017d

Component: piglit
    tag: piglit-v1
    commit: dab15137044c34023b1a843e72e781b03b17548b



======================================
	     Software
======================================
kernel version              : 4.13.0-drm-tip-ww36-commit-00f9b49+
hostname                    : SKL-2-NUC6i5SYB
architecture                : x86_64
os version                  : Ubuntu 16.10
os codename                 : yakkety
kernel driver               : i915
bios revision               : 5.6
bios release date           : 05/27/2016
hardware acceleration       : disabled
swap partition              : enabled on (/dev/sda3)

======================================
	Graphic drivers
======================================
libdrm                      : 2.4.83
cairo                       : 1.15.9
intel-gpu-tools (tag)       : intel-gpu-tools-1.19-244-g4a1c8da
intel-gpu-tools (commit)    : 4a1c8da

======================================
	     Hardware
======================================
platform                   : Skylake-Nuc
motherboard id             : NUC6i5SYB
form factor                : Desktop
cpu family                 : Core i5
cpu family id              : 6
cpu information            : Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz
gpu card                   : Intel Corporation Iris Graphics 540 (rev 0a) (prog-if 00 [VGA controller])
memory ram                 : 15.56 GB
max memory ram             : 32 GB
cpu thread                 : 4
cpu core                   : 2
cpu model                  : 78
cpu stepping               : 3
socket                     : None
signature                  : Type 0, Family 6, Model 78, Stepping 3
hard drive                 : 223GiB (240GB)
current cd clock frequency : 337500 kHz
maximum cd clock frequency : 675000 kHz
displays connected         : HDMI-A-1 DP-1

======================================
	     Firmware
======================================
dmc fw loaded             : yes
dmc version               : 1.26
guc fw loaded             : SUCCESS
guc version wanted        : 6.1
guc version found         : 6.1

======================================
	     kernel parameters
======================================
quiet drm.debug=0x1e pci=pcie_bus_safe intel_iommu=igfx_off auto panic=1 i915.alpha_support=1 i915.enable_guc_loading=2 i915.enable_guc_submission=2 nmi_watchdog=panic resume=/dev/sda3 fastboot

Note: this is related to the Bug 101188 mark as closed/fixed
Comment 1 Hector Velazquez 2017-09-07 15:16:00 UTC
Created attachment 134046 [details]
Dmesg log
Comment 2 Chris Wilson 2017-09-07 17:47:59 UTC

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


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.