Bug 97188 - [BAT] kms_cursor_legacy/basic-flip-vs-cursor-legacy Failed assertion: get_vblank(display->drm_fd, pipe, 0) == vblank_start
Summary: [BAT] kms_cursor_legacy/basic-flip-vs-cursor-legacy Failed assertion: get_vbl...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: highest blocker
Assignee: Luis Botello
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-02 13:18 UTC by Ville Syrjala
Modified: 2016-09-09 09:49 UTC (History)
1 user (show)

See Also:
i915 platform: ALL
i915 features: display/atomic


Attachments
dmesg (39.74 KB, text/plain)
2016-08-26 18:50 UTC, Luis Botello
no flags Details
IGTuotput.log (6.91 KB, text/plain)
2016-08-26 18:51 UTC, Luis Botello
no flags Details

Description Ville Syrjala 2016-08-02 13:18:27 UTC
(kms_cursor_legacy:8712) DEBUG: Test requirement passed: target > 1
(kms_cursor_legacy:8712) DEBUG: Using a target of 64 cursor updates per half-vblank
(kms_cursor_legacy:8712) CRITICAL: Test assertion failure function basic_flip_vs_cursor, file kms_cursor_legacy.c:514:
(kms_cursor_legacy:8712) CRITICAL: Failed assertion: get_vblank(display->drm_fd, pipe, 0) == vblank_start
(kms_cursor_legacy:8712) CRITICAL: error: 11091 != 11090

Seems to happen on most platforms.
Comment 1 Luis Botello 2016-08-26 18:49:48 UTC
This issue is also seen on BSW with the following config:

Software Configuration:
============================================
Kernel: 4.8.0-rc3 from http://cgit.freedesktop.org/drm-intel/
    commit f53a8d1853e8a97ad4a6308ffa8a2011fbd80467
    Author: Chris Wilson <chris@chris-wilson.co.uk>
    Date:   Fri Aug 19 17:24:52 2016 +0100
    drm-intel-nightly: 2016y-08m-19d-16h-24m-21s UTC integration manifest
libdrm-2.4.70-2 b214b05 from git://anongit.freedesktop.org/mesa/drm
mesa: mesa-11.2.2 3a9f628from git://anongit.freedesktop.org/mesa/mesa
cairo 1.15.2 db8a7f1 from git://anongit.freedesktop.org/cairo
xorg-server-1.18.0- 532 6e5bec2 from git://git.freedesktop.org/git/xorg/xserver
xf86-video-intel 2.99.697 12c14de from git://git.freedesktop.org/git/xorg/driver/xf86-video-intel
libva-1.7.0-45 b27feb9 from git://git.freedesktop.org/git/vaapi/libva 
vaapi-intel-driver: 1.7.0-89 b53fad9 from git://git.freedesktop.org/git/vaapi/intel-driver
Intel-Gpu-Tools 1.15 a147ef2 from http://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git

Hardware Configuration:
=============================================
Hardware: Acer Desktop
Motherboard: Aspire XC-704
CPU: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz (Family 6, Model 76, Stepping 3)
GPU:  Intel® HD Graphics - Intel Corporation Device 22b1 (rev 21)
Memory card: 1 card 4GB Hynix HMT451S6BFR8APB
HDD: Western Digital WDC WD10EZEX-21M (1TB)

Software:
Bios: R01-A2
Linux distribution: Ubuntu 16.04 64 bits

Test cases:
=============================================
kms_cursor_legacy@basic-flip-vs-cursor-varying-size
kms_cursor_legacy@long-flip-vs-cursor-legacy
kms_cursor_legacy@long-flip-vs-cursor-toggle
kms_cursor_legacy@long-flip-vs-cursor-varying-size
kms_cursor_legacy@short-flip-vs-cursor-toggle

Please see the attachments dmesg and IGToutput.log
Comment 2 Luis Botello 2016-08-26 18:50:57 UTC
Created attachment 126058 [details]
dmesg
Comment 3 Luis Botello 2016-08-26 18:51:11 UTC
Created attachment 126059 [details]
IGTuotput.log
Comment 4 Jari Tahvanainen 2016-09-08 10:51:51 UTC
Both basic-flip-vs-cursor-legacy and basic-flip-vs-cursor-varying-size have been pass on CI on all machines for more than couple weeks. Luis - please check and/or retest.
Comment 5 yann 2016-09-09 09:49:51 UTC
(In reply to Jari Tahvanainen from comment #4)
> Both basic-flip-vs-cursor-legacy and basic-flip-vs-cursor-varying-size have
> been pass on CI on all machines for more than couple weeks. Luis - please
> check and/or retest.

Confirm that on QA side both basic-flip-vs-cursor-legacy and basic-flip-vs-cursor-varying-size are passing on all machines as well


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.