Bug 100917

Summary: [IGT] [BYT/BSW] igt@kms_flip@bo-too-big* Last errno: 7, Argument list too long
Product: DRI Reporter: Luis Botello <luis.botello.ortega>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard: ReadyForDev
i915 platform: BSW/CHT, BYT i915 features: display/Other
Attachments:
Description Flags
dmesg
none
IGToutput
none
IGT Output form BYT and BSW
none
dmesg_log_BSW_bo-too-big
none
attachment-30122-0.html
none
dmesg_log_BYT_bo-too-big
none
Test_outputs_bo-too-big none

Description Luis Botello 2017-05-03 17:03:02 UTC
Created attachment 131188 [details]
dmesg

==Bug detailed description==
--------------------------------------------------
kms_flip@bo-too-big* tests produce a test assertion failure function run_test_on_crtc_set

==Steps to reproduce==
--------------------------------------------------
./kms_flip --run-subtest bo-too-big

==Actual results==
--------------------------------------------------
Test result is fail

==Expected results==
--------------------------------------------------
Test result must be pass

==Hardware configuration==
--------------------------------------------------
platform                   : BYT-M (Toshiba)
motherboard model          : SatelliteC55t-A
motherboard id             : PortablePC
form factor                : Notebook
manufacturer               : TOSHIBA
cpu family                 : Atom
cpu family id              : 6
cpu information            : Intel(R) Celeron(R) CPU  N2820  @ 2.13GHz
gpu card                   : Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display (rev 0c) (prog-if 00 [VGA controller])
memory ram                 : 3.72 GB
signature                  : Type 0, Family 6, Model 55, Stepping 3
displays connected         : eDP-1 HDMI-A-1

==Software configuration==
--------------------------------------------------
kernel version              : 4.11.0-rc8-drm-tip-ww18-commit-aea271f+
architecture                : x86_64
os version                  : Ubuntu 16.10
kernel driver               : i915
bios revision               : 1.30
libdrm                      : 2.4.80
cairo                       : 1.15.5
intel-gpu-tools (tag)       : intel-gpu-tools-1.18-113-g529c0d1
intel-gpu-tools (commit)    : 529c0d1

==kernel configuration==
--------------------------------------------------
commit aea271f0b4bbc3450fa2e3e644ef756dd1c55a3d
Author:     Gustavo Padovan <gustavo.padovan@collabora.com>
AuthorDate: Wed May 3 12:17:30 2017 -0300
Commit:     Gustavo Padovan <gustavo.padovan@collabora.com>
CommitDate: Wed May 3 12:17:30 2017 -0300
    drm-tip: 2017y-05m-03d-15h-13m-14s UTC integration manifest

==Attachments==
--------------------------------------------------
dmesg
IGToutput
Comment 1 Luis Botello 2017-05-03 17:03:21 UTC
Created attachment 131189 [details]
IGToutput
Comment 2 Humberto Israel Perez Rodriguez 2017-05-31 15:37:57 UTC
Same issue on BSW with the latest configuration

igt@kms_flip@bo-too-big

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
Comment 3 Hector Velazquez 2017-07-31 19:05:54 UTC
The following tests FAIL on BSW with this configuration

Tests List:

igt@kms_flip@bo-too-big
igt@kms_flip@bo-too-big-interruptible



This is my configuration:

**************************************************************
* * * * * * * * HARDWARE SPECIFICATIONS * * * * * * * * * * * 
**************************************************************

==============================================================
Essentials
==============================================================
Processor Number			N3700
Status					Launched
Launch Date				Q1'15
Lithography				14 nm


==============================================================
Performance
==============================================================
# of Cores				4
# of Threads				4
Processor Base Frequency		1.60 GHz
Burst Frequency				2.40 GHz
Cache					2 MB L2
TDP					6 W
Scenario Design Power (SDP)		4 W

==============================================================
Memory Specifications
==============================================================
Max Memory Size 			8 GB
Memory Types				DDR3L-1600
Max # of Memory Channels		2
ECC Memory Supported  			No

==============================================================
Graphics Specifications
==============================================================
Processor Graphics 			Intel® HD Graphics
Graphics Base Frequency			400.00 MHz
Graphics Burst Frequency		700.00 MHz
Graphics Video Max Memory		8 GB
Graphics Output				eDP/DP/HDMI
Execution Units				16
DirectX* Support			Yes
OpenGL* Support				Yes
Intel® Quick Sync Video 		Yes
Intel® InTru™ 3D Technology		No
Intel® Clear Video HD Technology	Yes
Intel® Clear Video Technology		Yes
Intel® Wireless Display 		Yes
# of Displays Supported 		3


====================================================
Graphic Stack
====================================================

Component: drm
    tag: libdrm-2.4.81-33-g3876bc2
    commit: 3876bc246a07070a6043159cd7623d4def9bbd4c

Component: cairo
    tag: 1.15.6-2-g57b4050
    commit: 57b40507dda3f58dfc8635548d606b86dc7bcf51

Component: intel-gpu-tools
    tag: intel-gpu-tools-1.19-112-g493151b
    commit: 493151b0768aa4ca535cef49cb7efa174a9c3a77

Component: piglit
    tag: piglit-v1
    commit: 973892687cf5c2f8e2dbe1d22998b82736643787
Comment 4 Elizabeth 2017-10-11 21:24:56 UTC
Created attachment 134801 [details]
IGT Output form BYT and BSW

The tests keep failing at BYT and BSW with
IGT-Version: 1.20-g136100c (x86_64) (Linux: 4.14.0-rc4-drm-intel-qa-ww41-commit-36e0e80+ x86_64).
Comment 5 Chris Wilson 2017-12-12 10:46:12 UTC
commit 74407418720ff7a9de7caabec05d4c3afe9a5c51 (upstream/master, origin/master, origin/HEAD)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Dec 11 17:18:23 2017 +0000

    igt/kms_flip: Allow very large bo to fail pageflips with E2BIG
    
    We tried to allow very large buffers (larger than the mappable aperture)
    to be flippable by allowing them to be bound into the unmappable region.
    Sadly, not all of our hw is capable of utilising the unmappable region for
    scanout (and on some older hw, there is only mappable). As such, we have
    to allow the very large bo to either succeed in being flipped, or fail
    with the expected E2BIG.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=100917
    References: 9d5e393da3f5 ("igt/kms_flip: There's no such thing as bo-too-big")
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Comment 6 Elizabeth 2017-12-27 23:35:27 UTC
Created attachment 136411 [details]
dmesg_log_BSW_bo-too-big

Tests keep failing though assertions are different now:

(02:31 AM) [gfx@BSW-1-BRASWELL] [tests]$ : time sudo -E ./kms_flip --run-subtest bo-too-big*
IGT-Version: 1.20-g4cd4cc4 (x86_64) (Linux: 4.15.0-rc5-drm-tip-ww52-commit-42a41a5+ x86_64)
Using monotonic timestamps
Beginning bo-too-big on pipe A, connector DP-1
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 0x5 0x48 148500
(kms_flip:6600) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1336:
(kms_flip:6600) CRITICAL: Failed assertion: err == 0 || err == -E2BIG
(kms_flip:6600) CRITICAL: Last errno: 28, No space left on device
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [run_test_on_crtc_set.constprop.14+0x1dfc]
  #2 [run_test+0x26a]
  #3 [main+0x10b]
  #4 [__libc_start_main+0xf1]
  #5 [_start+0x29]
  #6 [<unknown>+0x29]
Subtest bo-too-big failed.
Comment 7 Luis Botello 2017-12-27 23:35:34 UTC
Created attachment 136412 [details]
attachment-30122-0.html

Hi, I am OOO  (holidays/vacations), I will return back on WW01.2 (Tuesday, January 02).

Best Regards!
Luis Botello
Comment 8 Elizabeth 2017-12-27 23:37:26 UTC
Created attachment 136413 [details]
dmesg_log_BYT_bo-too-big
Comment 9 Elizabeth 2017-12-27 23:39:37 UTC
Created attachment 136414 [details]
Test_outputs_bo-too-big
Comment 10 Elizabeth 2018-03-05 22:58:58 UTC
These tests are no more failed. Should have been fixed between commits 8a1ed24 and 562dc33.

Our latest bad result:

IGT-Version: 1.21-g2b64cac (x86_64) (Linux: 4.16.0-rc1-drm-intel-qa-ww7-commit-8a1ed24+ x86_64)
Using monotonic timestamps
Beginning bo-too-big-interruptible on pipe A, connector DP-1
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 0x5 0x48 148500
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [run_test_on_crtc_set.constprop.14+0x1a94]
  #2 [run_test+0x26a]
  #3 [main+0x4d8]
  #4 [__libc_start_main+0xf1]
  #5 [_start+0x29]
  #6 [<unknown>+0x29]
Subtest bo-too-big-interruptible: FAIL (1.036s)

Our first good:

IGT-Version: 1.21-g1fb30f1 (x86_64) (Linux: 4.16.0-rc2-drm-intel-qa-ww8-commit-562dc33+ x86_64)
Using monotonic timestamps
Beginning bo-too-big-interruptible on pipe A, connector DP-1
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 0x5 0x48 148500
Beginning bo-too-big-interruptible on pipe B, connector DP-1
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 0x5 0x48 148500
Beginning bo-too-big-interruptible on pipe C, connector DP-3
  1024x768 60 1024 1048 1184 1344 768 771 777 806 0xa 0x40 65000
Subtest bo-too-big-interruptible: SUCCESS (3.711s)

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.