[Bug 101636] [IGT] [IVB] kms_concurrent some subtest causes assertion failure
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Sep 28 12:30:37 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=101636
--- Comment #10 from Hector Velazquez <hector.franciscox.velazquez.suriano at intel.com> ---
This test is still failing on GLK QA
Tests List:
igt at kms_concurrent@pipe-A
igt at kms_concurrent@pipe-B
igt at kms_concurrent@pipe-C
====================================================
Output
====================================================
. . .
**** DEBUG ****
(kms_concurrent:16084) INFO: Testing resolution with connector eDP-1 using pipe
A with seed 1506601353
(kms_concurrent:16084) igt-kms-DEBUG: display: eDP-1: set_pipe(A)
(kms_concurrent:16084) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
76 to 1
(kms_concurrent:16084) igt-kms-DEBUG: display: eDP-1: Selecting pipe A
(kms_concurrent:16084) igt-kms-DEBUG: Test requirement passed: plane_idx >= 0
&& plane_idx < pipe->n_planes
(kms_concurrent:16084) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1920,
height=1080, format=0x34325258, tiling=0x100000000000001, size=0)
(kms_concurrent:16084) drmtest-DEBUG: Test requirement passed:
is_i915_device(fd) && has_known_intel_chipset(fd)
(kms_concurrent:16084) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=1,
pitch=7680)
(kms_concurrent:16084) igt-kms-DEBUG: display: A.0: plane_set_fb(78)
(kms_concurrent:16084) igt-kms-DEBUG: display: commit {
(kms_concurrent:16084) igt-kms-DEBUG: display: A: Setting mode 1920x1080
from eDP-1
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.0,
fb 78
(kms_concurrent:16084) igt-kms-DEBUG: display: src = (0, 0) 1920 x 1080 dst
= (0, 0) 1920 x 1080
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.1,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.2,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.3,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.4,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: B: Setting NULL mode
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.0,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.1,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.2,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.3,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.4,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: C: Setting NULL mode
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.0,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.1,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.2,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.3,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.4,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: eDP-1: preparing atomic,
pipe: A
(kms_concurrent:16084) igt-kms-DEBUG: display: DP-1: preparing atomic,
pipe: None
(kms_concurrent:16084) igt-kms-DEBUG: display: HDMI-A-1: preparing atomic,
pipe: None
(kms_concurrent:16084) igt-kms-DEBUG: display: HDMI-A-2: preparing atomic,
pipe: None
(kms_concurrent:16084) igt-kms-DEBUG: display: }
(kms_concurrent:16084) DEBUG: Test requirement passed: !(ret != 0)
(kms_concurrent:16084) igt-kms-DEBUG: display: eDP-1: set_pipe(A)
(kms_concurrent:16084) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
76 to 1
(kms_concurrent:16084) igt-kms-DEBUG: display: eDP-1: Selecting pipe A
(kms_concurrent:16084) igt-kms-DEBUG: display: commit {
(kms_concurrent:16084) igt-kms-DEBUG: display: A: Setting mode Custom
1024x768 from eDP-1
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.0,
fb 78
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.1,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.2,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.3,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: A.4,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.0,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.1,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.2,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.3,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: B.4,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.0,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.1,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.2,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.3,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: populating plane data: C.4,
fb 0
(kms_concurrent:16084) igt-kms-DEBUG: display: eDP-1: preparing atomic,
pipe: A
(kms_concurrent:16084) igt-kms-DEBUG: display: DP-1: preparing atomic,
pipe: None
(kms_concurrent:16084) igt-kms-DEBUG: display: HDMI-A-1: preparing atomic,
pipe: None
(kms_concurrent:16084) igt-kms-DEBUG: display: HDMI-A-2: preparing atomic,
pipe: None
(kms_concurrent:16084) igt-kms-DEBUG: display: }
(kms_concurrent:16084) igt-kms-CRITICAL: Test assertion failure function
do_display_commit, file igt_kms.c:2681:
(kms_concurrent:16084) igt-kms-CRITICAL: Failed assertion: ret == 0
(kms_concurrent:16084) igt-kms-CRITICAL: Last errno: 22, Invalid argument
(kms_concurrent:16084) igt-kms-CRITICAL: error: -22 != 0
(kms_concurrent:16084) igt-core-INFO: Stack trace:
(kms_concurrent:16084) igt-core-INFO: #0 [__igt_fail_assert+0x101]
(kms_concurrent:16084) igt-core-INFO: #1 [do_display_commit+0xa14]
(kms_concurrent:16084) igt-core-INFO: #2 [<unknown>+0xa14]
**** END ****
. . .
This is my configuration:
======================================
Graphic stack
======================================
Component: drm
tag: libdrm-2.4.81-56-g7c71188
commit: 7c71188610b4ceba0339c2bc884320bcb749adee
Component: cairo
tag: 1.15.6-42-gdccbed7
commit: dccbed7d78d32bd3b912e8810379451dd94e6a1f
Component: intel-gpu-tools
tag: intel-gpu-tools-1.19-332-g0a91a5e
commit: 0a91a5e9624d41d23b79e2540eda111cb56d42d9
Component: piglit
tag: piglit-v1
commit: 95e2f51a28b6cf7ff77d84e1234121c98f10ef64
======================================
Software
======================================
kernel version : 4.14.0-rc2-drm-tip-ww39-commit-d76cbbc+
hostname : GLK-2-GLKRVP1DDR405
architecture : x86_64
os version : Ubuntu 16.10
os codename : yakkety
kernel driver : i915
bios revision : 62.30
bios release date : 08/22/2017
ksc : 1.41
hardware acceleration : disabled
swap partition : enabled on (/dev/sda3)
======================================
Graphic drivers
======================================
grep: /opt/X11R7/var/log/Xorg.0.log: No such file or directory
libdrm : 2.4.83
cairo : 1.15.9
intel-gpu-tools (tag) : intel-gpu-tools-1.19-332-g0a91a5e
intel-gpu-tools (commit) : 0a91a5e
======================================
Hardware
======================================
. . .
======================================
Firmware
======================================
dmc fw loaded : yes
dmc version : 1.4
guc fw loaded : SUCCESS
guc version wanted : 10.56
guc version found : 10.56
huc fw loaded : yes
======================================
kernel parameters
======================================
quiet drm.debug=0xe pci=pcie_bus_safe i915.alpha_support=1
i915.enable_guc_loading=2 i915.enable_guc_submission=2 intel_iommu=igfx_off
auto panic=1 nmi_watchdog=panic resume=/dev/sda3 fastboot
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170928/8cd5e3fa/attachment.html>
More information about the intel-gfx-bugs
mailing list