From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92248] [KBL/SKL/BYT/BXT/GLK] igt/kms_plane_scaling fail
Date: Fri, 29 Sep 2017 19:46:26 +0000 [thread overview]
Message-ID: <bug-92248-502-ClYnTo2vt0@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92248-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 8495 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92248
--- Comment #43 from Hector Velazquez <hector.franciscox.velazquez.suriano@intel.com> ---
This test are failing on CFL-S-1 QA
Tests List:
igt@kms_plane_scaling
====================================================
Output
====================================================
. . .
**** DEBUG ****
(kms_plane_scaling:2699) igt-core-INFO: IGT-Version: 1.19-g2885b10 (x86_64)
(Linux: 4.14.0-rc2-drm-tip-ww39-commit-85932e1+ x86_64)
(kms_plane_scaling:2699) igt-core-DEBUG: Test requirement passed:
!igt_run_in_simulation()
(kms_plane_scaling:2699) drmtest-DEBUG: Test requirement passed: !(fd<0)
(kms_plane_scaling:2699) igt-debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(kms_plane_scaling:2699) igt-debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(kms_plane_scaling:2699) igt-kms-DEBUG: display: init {
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
48 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
56 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
61 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
65 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
68 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
72 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: display: }
(kms_plane_scaling:2699) DEBUG: Test requirement passed: d->num_scalers
(kms_plane_scaling:2699) igt-kms-DEBUG: display: eDP-1: set_pipe(A)
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
48 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: display: eDP-1: Selecting pipe A
(kms_plane_scaling:2699) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1920,
height=1080, format=0x34325258, tiling=0x100000000000001, size=0)
(kms_plane_scaling:2699) drmtest-DEBUG: Test requirement passed:
is_i915_device(fd) && has_known_intel_chipset(fd)
(kms_plane_scaling:2699) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=1,
pitch=7680)
(kms_plane_scaling:2699) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1920,
height=1080, format=0x34325258, tiling=0x100000000000001, size=0)
(kms_plane_scaling:2699) drmtest-DEBUG: Test requirement passed:
is_i915_device(fd) && has_known_intel_chipset(fd)
(kms_plane_scaling:2699) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=2,
pitch=7680)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: eDP-1: set_pipe(A)
(kms_plane_scaling:2699) igt-kms-DEBUG: Setting Broadcast RGB mode on connector
48 to 1
(kms_plane_scaling:2699) igt-kms-DEBUG: display: eDP-1: Selecting pipe A
(kms_plane_scaling:2699) igt-debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(kms_plane_scaling:2699) igt-debugfs-DEBUG: Using generic frame CRC ABI
(kms_plane_scaling:2699) igt-fb-DEBUG: igt_create_fb_with_bo_size(width=1920,
height=1080, format=0x34325258, tiling=0x100000000000001, size=0)
(kms_plane_scaling:2699) drmtest-DEBUG: Test requirement passed:
is_i915_device(fd) && has_known_intel_chipset(fd)
(kms_plane_scaling:2699) igt-fb-DEBUG: igt_create_fb_with_bo_size(handle=3,
pitch=7680)
(kms_plane_scaling:2699) igt-kms-DEBUG: Test requirement passed: plane_idx >= 0
&& plane_idx < pipe->n_planes
(kms_plane_scaling:2699) igt-kms-DEBUG: display: A.0: plane_set_fb(84)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: A.1: plane_set_fb(84)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: commit {
(kms_plane_scaling:2699) igt-kms-DEBUG: display: SetPlane A.0, fb 84, src =
(0, 0) 1920x1080 dst = (0, 0) 1920x1080
(kms_plane_scaling:2699) igt-kms-DEBUG: display: SetPlane A.1, fb 84, src =
(0, 0) 1920x1080 dst = (0, 0) 1920x1080
(kms_plane_scaling:2699) igt-kms-DEBUG: display: SetPlane pipe A, plane 2,
disabling
(kms_plane_scaling:2699) igt-kms-DEBUG: display: SetPlane pipe B, plane 0,
disabling
(kms_plane_scaling:2699) igt-kms-DEBUG: display: SetPlane pipe B, plane 1,
disabling
(kms_plane_scaling:2699) igt-kms-DEBUG: display: SetPlane pipe B, plane 2,
disabling
(kms_plane_scaling:2699) igt-kms-DEBUG: display: }
(kms_plane_scaling:2699) igt-kms-DEBUG: display: A.2: plane_set_fb(76)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: A.2: fb_set_position(100,100)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: A.2: fb_set_size(1720x880)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: A.2:
plane_set_position(100,100)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: A.2: plane_set_size (1720x880)
(kms_plane_scaling:2699) igt-kms-DEBUG: display: commit {
(kms_plane_scaling:2699) igt-kms-DEBUG: display: SetPlane A.2, fb 76, src =
(100, 100) 1720x880 dst = (100, 100) 1720x880
(kms_plane_scaling:2699) igt-kms-CRITICAL: Test assertion failure function
igt_drm_plane_commit, file igt_kms.c:2245:
(kms_plane_scaling:2699) igt-kms-CRITICAL: Failed assertion: ret == 0
(kms_plane_scaling:2699) igt-kms-CRITICAL: Last errno: 22, Invalid argument
(kms_plane_scaling:2699) igt-kms-CRITICAL: error: -22 != 0
(kms_plane_scaling:2699) igt-core-INFO: Stack trace:
(kms_plane_scaling:2699) igt-core-INFO: #0 [__igt_fail_assert+0x101]
(kms_plane_scaling:2699) igt-core-INFO: #1 [do_display_commit+0xa9c]
(kms_plane_scaling:2699) igt-core-INFO: #2 [<unknown>+0xa9c]
**** 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-334-g2885b10
commit: 2885b10f99b4beeb046e75af8b8488c229f629d3
Component: piglit
tag: piglit-v1
commit: e1f66fb2fb8ad781ca755831983b6662c4c440d4
======================================
Software
======================================
kernel version : 4.14.0-rc2-drm-tip-ww39-commit-85932e1+
hostname : CFL-S-1
architecture : x86_64
os version : Ubuntu 16.10
os codename : yakkety
kernel driver : i915
bios revision : 104.3
bios release date : 09/14/2017
ksc : 1.5
hardware acceleration : disabled
swap partition : enabled on (/dev/sda3
/dev/nvme0n1p3)
======================================
Graphic drivers
======================================
libdrm : 2.4.83
cairo : 1.15.9
intel-gpu-tools (tag) : intel-gpu-tools-1.19-334-g2885b10
intel-gpu-tools (commit) : 2885b10
======================================
Hardware
======================================
motherboard model : CoffeeLakeClientPlatform
motherboard id : CoffeeLakeSUDIMMRVP
form factor : Desktop
manufacturer : IntelCorporation
cpu family : Other
cpu family id : 6
cpu information : Genuine Intel(R) CPU 0000 @ 3.60GHz
gpu card : Intel Corporation Device 3e92 (prog-if 00 [VGA
controller])
memory ram : 15.58 GB
max memory ram : 32 GB
cpu thread : 12
cpu core : 6
cpu model : 158
cpu stepping : 10
socket : Other
hard drive : 111GiB (120GB)
current cd clock frequency : 337500 kHz
maximum cd clock frequency : 675000 kHz
displays connected : eDP-1 DP-1
======================================
Firmware
======================================
dmc fw loaded : yes
dmc version : 1.1
guc fw loaded : SUCCESS
guc version wanted : 9.14
guc version found : 9.14
======================================
kernel parameters
======================================
quiet drm.debug=0xe pci=pcie_bus_safe intel_iommu=igfx_off auto panic=1
nmi_watchdog=panic i915.alpha_support=1 i915.enable_guc_loading=2
i915.enable_guc_submission=2 resume=/dev/sda3 fastboot
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 9386 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-29 19:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92248-502@http.bugs.freedesktop.org/>
2016-06-28 13:29 ` [Bug 92248] [KBL/SKL/BYT/BXT] igt/kms_plane_scaling fail bugzilla-daemon
2016-06-29 17:26 ` bugzilla-daemon
2016-07-08 15:45 ` bugzilla-daemon
2016-09-15 14:59 ` bugzilla-daemon
2016-10-13 22:02 ` bugzilla-daemon
2016-10-20 22:10 ` bugzilla-daemon
2017-03-21 10:49 ` bugzilla-daemon
2017-03-28 14:22 ` bugzilla-daemon
2017-05-18 0:02 ` bugzilla-daemon
2017-08-31 13:13 ` bugzilla-daemon
2017-08-31 13:14 ` [Bug 92248] [KBL/SKL/BYT/BXT/GLK] " bugzilla-daemon
2017-08-31 13:16 ` bugzilla-daemon
2017-08-31 13:17 ` bugzilla-daemon
2017-09-06 14:36 ` bugzilla-daemon
2017-09-06 14:37 ` bugzilla-daemon
2017-09-06 19:05 ` bugzilla-daemon
2017-09-19 22:20 ` bugzilla-daemon
2017-09-20 16:42 ` bugzilla-daemon
2017-09-28 12:39 ` bugzilla-daemon
2017-09-29 19:46 ` bugzilla-daemon [this message]
2017-11-08 14:59 ` bugzilla-daemon
2017-11-17 22:26 ` bugzilla-daemon
2017-11-29 20:14 ` bugzilla-daemon
2018-08-31 11:32 ` bugzilla-daemon
2018-08-31 11:32 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-92248-502-ClYnTo2vt0@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).