Bug 97050 - [KBL] some prime_busy subcases fail
Summary: [KBL] some prime_busy subcases fail
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-22 21:19 UTC by maria guadalupe
Modified: 2016-08-03 17:12 UTC (History)
1 user (show)

See Also:
i915 platform: KBL
i915 features: GEM/Other, GPU hang


Attachments
kern.log (103.18 KB, text/plain)
2016-07-22 21:19 UTC, maria guadalupe
no flags Details

Description maria guadalupe 2016-07-22 21:19:33 UTC
Created attachment 125263 [details]
kern.log

Executed IGT as part of the KBL PV execution, and the following subtests failed under the prime_busy family.

======== Steps to reproduce =====


# ./prime_busy --run-subtest basic-before-default
# ./prime_busy --run-subtest basic-wait-before-default
# ./prime_busy --run-subtest hang-bsd
# ./prime_busy --run-subtest hang-render
# ./prime_busy --run-subtest wait-after-blt
# ./prime_busy --run-subtest wait-after-bsd
# ./prime_busy --run-subtest wait-before-blt
# ./prime_busy --run-subtest wait-before-bsd
# ./prime_busy --run-subtest wait-before-render
# ./prime_busy --run-subtest wait-before-vebox
# ./prime_busy --run-subtest wait-hang-blt
# ./prime_busy --run-subtest wait-hang-bsd
# ./prime_busy --run-subtest wait-hang-render
# ./prime_busy --run-subtest wait-hang-vebox

Expected output
=============================
Tests should pass

Actual Ouput
============================
Tests Fail showing the following errors: 

**** DEBUG ****
(prime_busy:2823) DEBUG: Test requirement passed: __gem_execbuf(fd, &execbuf) == 0
(prime_busy:2823) CRITICAL: Test assertion failure function busy, file prime_busy.c:138:
(prime_busy:2823) CRITICAL: Failed assertion: prime_busy(&pfd[SCRATCH], false)
****  END  ****


 Software information
============================================
Kernel version                  : 4.7.0-rc7-nightly
Linux distribution              : Ubuntu 16.04 LTS
Architecture                    : 64-bit
xf86-video-intel version        : 2.99.917
Xorg-Xserver version            : 1.18.99.1
DRM version                     : 2.4.68
VAAPI version                   : Intel i965 driver for Intel(R) Kabylake - 1.7.2.pre1 (1.7.0-53-gbcde10d)
Cairo version                   : 1.15.2
Intel GPU Tools version         : Tag [intel-gpu-tools-1.15-127-gee5d5c4] / Commit [ee5d5c4]
Kernel driver in use            : i915
Bios revision                   : 38.7
KSC revision                    : 1.20


 Hardware information
============================================
Platform                        : KBL (RVP7)
Motherboard model               : Kabylake Client platform
Motherboard type                : Skylake U DDR3L RVP7 Laptop
Motherboard manufacturer        : Intel Corporation
CPU family                      : Other
CPU information                 : Genuine Intel(R) CPU 0000 @ 2.60GHz
GPU Card                        : Intel Corporation Device 5916 (prog-if 00 [VGA controller])
Memory ram                      : 4 GB
Maximum memory ram allowed      : 16 GB
CPU's number                    : 4
Hard drive Capacity             : 80.0 GB

 Firmwares information
============================================
DMC fw loaded                   : yes
DMC version                     : 1.1
GUC version wanted              : 9.14
GUC version found               : 9.14

 Kernel parameters
============================================
 quiet splash drm.debug=0xe


please see the attachment kern.log
Comment 1 cprigent 2016-07-25 15:47:16 UTC
It could be the same as bug 96751 and/or bug 97076.

Maria,
Could you attach the file /sys/class/drm/card0/error
Comment 2 yann 2016-08-03 17:12:13 UTC
Closing this bug due to lack of information. Maria, please reopen if you are facing again the issue (and check whether or not this is not duplicate of: bug 97076)


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.