Bug 100730 - [GLK - IGT] [regression] igt@kms_frontbuffer_tracking@basic
Summary: [GLK - IGT] [regression] igt@kms_frontbuffer_tracking@basic
Status: CLOSED DUPLICATE of bug 100728
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords: bisect_pending, regression
Depends on:
Blocks:
 
Reported: 2017-04-19 23:49 UTC by maria guadalupe
Modified: 2017-06-27 14:24 UTC (History)
2 users (show)

See Also:
i915 platform: GLK
i915 features: display/Other


Attachments
dmesg1.log (128.65 KB, text/plain)
2017-04-19 23:49 UTC, maria guadalupe
no flags Details

Description maria guadalupe 2017-04-19 23:49:17 UTC
Created attachment 130934 [details]
dmesg1.log

the following sub-test is failing over GLK with the below configuration.

 Regression: yes 

Software
======================================
kernel version              : 4.11.0-rc7-drm-tip-ww16-commit-1b75708+
architecture                : x86_64
os version                  : Ubuntu 16.10
os codename                 : yakkety
kernel driver               : i915
bios revision               : 43.30
bios release date           : 04/11/2017
ksc                         : 1.25

======================================
        Graphic drivers
======================================
modesetting                 : modesetting_drv.so
modesetting_drv.so
xorg-xserver                : 1.18.4
libdrm                      : 2.4.80
vaapi (intel-driver)        : Intel i965 driver for Intel(R) Geminilake - 1.8.2.pre1 (1.7.3-382-gdbe582c)
cairo                       : 1.15.5
xserver                     : X.Org X Server 1.19.99.1
intel-gpu-tools (tag)       : intel-gpu-tools-1.18-86-gac1fe09
intel-gpu-tools (commit)    : ac1fe09

======================================
             Hardware
======================================
platform                  : Geminilake
motherboard model          : Geminilake
motherboard id             : GLKRVP1DDR4(05)
form factor                : Hand Held
manufacturer               : IntelCorp.
cpu family                 : Other
cpu family id              : 6
cpu information            : Genuine Intel(R) CPU @ 1.10GHz
gpu card                   : Intel Corporation Device 3184 (rev 01) (prog-if 00 [VGA controller])
memory ram                 : 3.67 GB
max memory ram             : 16 GB
xdpyinfo:  unable to open display ":0".
cpu thread                 : 4
cpu core                   : 4
cpu model                  : 122
hard drive                 : 111GiB (120GB)
current cd clock frequency : 316800 kHz
maximum cd clock frequency : 316800 kHz
displays connected         : eDP-1 DP-1 HDMI-A-2

======================================
             Firmware
======================================
dmc fw loaded             : yes
dmc version               : 1.4

OUTPUT
======================================
./kms_frontbuffer_tracking --r b           asic --debug
IGT-Version: 1.18-gac1fe09 (x86_64) (Linux: 4.11.0-rc7-drm-tip-ww16-commit-1b757           08+ x86_64)
(kms_frontbuffer_tracking:1350) drmtest-DEBUG: Test requirement passed: !(fd<0)
(kms_frontbuffer_tracking:1350) igt-debugfs-DEBUG: Opening debugfs directory '/s           ys/kernel/debug/dri/0'
(kms_frontbuffer_tracking:1350) drmtest-DEBUG: Test requirement passed: drmSetMa           ster(fd) == 0
(kms_frontbuffer_tracking:1350) igt-debugfs-DEBUG: Opening debugfs directory '/s           ys/kernel/debug/dri/0'
(kms_frontbuffer_tracking:1350) DEBUG: Test requirement passed: rc == 0
(kms_frontbuffer_tracking:1350) CRITICAL: Test assertion failure function setup_           drm, file kms_frontbuffer_tracking.c:1374:
(kms_frontbuffer_tracking:1350) CRITICAL: Failed assertion: drm.bufmgr
(kms_frontbuffer_tracking:1350) CRITICAL: Last errno: 2, No such file or directo           ry
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [setup_environment+0x8ef]
  #2 [main+0xc53]
  #3 [__libc_start_main+0xf1]
  #4 [_start+0x29]
  #5 [<unknown>+0x29]
Test kms_frontbuffer_tracking failed.
**** DEBUG ****
(kms_frontbuffer_tracking:1350) drmtest-DEBUG: Test requirement passed: !(fd<0)
(kms_frontbuffer_tracking:1350) igt-debugfs-DEBUG: Opening debugfs directory '/s           ys/kernel/debug/dri/0'
(kms_frontbuffer_tracking:1350) drmtest-DEBUG: Test requirement passed: drmSetMa           ster(fd) == 0
(kms_frontbuffer_tracking:1350) igt-debugfs-DEBUG: Opening debugfs directory '/s           ys/kernel/debug/dri/0'
(kms_frontbuffer_tracking:1350) DEBUG: Test requirement passed: rc == 0
(kms_frontbuffer_tracking:1350) CRITICAL: Test assertion failure function setup_           drm, file kms_frontbuffer_tracking.c:1374:
(kms_frontbuffer_tracking:1350) CRITICAL: Failed assertion: drm.bufmgr
(kms_frontbuffer_tracking:1350) CRITICAL: Last errno: 2, No such file or directo           ry
****  END  ****
Subtest basic: FAIL
Comment 1 Ander Conselvan de Oliveira 2017-04-24 11:10:51 UTC
(In reply to maria guadalupe from comment #0)
> Created attachment 130934 [details]
> dmesg1.log
> 
> the following sub-test is failing over GLK with the below configuration.
> 
>  Regression: yes 

What is the configuration with which the test passed?
Comment 2 maria guadalupe 2017-04-25 16:25:44 UTC
(In reply to Ander Conselvan de Oliveira from comment #1)
> (In reply to maria guadalupe from comment #0)
> > Created attachment 130934 [details]
> > dmesg1.log
> > 
> > the following sub-test is failing over GLK with the below configuration.
> > 
> >  Regression: yes 
> 
> What is the configuration with which the test passed?

this is the configuration with which the test passed.

Kernel version : 4.11.0-rc5-e461ecf
commit e461ecfd413fb930d00f44f3de0019e528b4731f
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Mon Apr 10 15:26:20 2017 +0100

drm-tip: 2017y-04m-10d-14h-25m-24s UTC integration manifest

Component         : drm
	tag       : libdrm-2.4.76-16-g6312017
	commit    : 6312017

Component         : cairo
	tag       : 1.15.4-11-gcffa452
	commit    : cffa452

Component         : intel-gpu-tools
	tag       : intel-gpu-tools-1.18-56-g56741ce
	commit    : 56741ce
Comment 3 cprigent 2017-04-28 09:23:06 UTC
Set to medium/normal until compilation problem is solved, tracked by VIZ-10567
Comment 4 krisman 2017-05-23 21:26:07 UTC

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


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.