Bug 98365

Summary: [BDW][Regression] gem_exec_alignment@single test fails
Product: DRI Reporter: Jairo Miramontes <jairo.daniel.miramontes.caton>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: BDW i915 features: GEM/Other
Attachments:
Description Flags
gem_exec_alignment single test logfile. none

Description Jairo Miramontes 2016-10-20 22:39:07 UTC 
Created attachment 127443 [details]
gem_exec_alignment single test logfile.

While executing IGT we found the below test regression on BDW, attached dmesg log file.

gem_exec_alignment@single

Output
========================================================================
(gem_exec_alignment:1223) CRITICAL: Test assertion failure function single, file gem_exec_align
(gem_exec_alignment:1223) CRITICAL: Failed assertion: execobj.offset % execobj.alignment == 0
(gem_exec_alignment:1223) CRITICAL: error: 0xfffff000 != 0
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [__real_main198+0x7b3]
  #2 [main+0x23]
  #3 [__libc_start_main+0xf0]
  #4 [_start+0x29]
  #5 [<unknown>+0x29]
Subtest single failed.
**** DEBUG ****
(gem_exec_alignment:1223) DEBUG: execbuffer() accepts non-power-of-two alignment? no
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffffff000, next alignment: 0x1000 [1
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffffff000, next alignment: 0x2000 [1
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffffffe000, next alignment: 0x4000 [1
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffffffc000, next alignment: 0x8000 [1
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffffff8000, next alignment: 0x10000 [
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffffff0000, next alignment: 0x20000 [
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffffe0000, next alignment: 0x40000 [
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffffc0000, next alignment: 0x80000 [
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffff80000, next alignment: 0x100000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffff00000, next alignment: 0x200000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffffe00000, next alignment: 0x400000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffffc00000, next alignment: 0x800000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffff800000, next alignment: 0x1000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffff000000, next alignment: 0x2000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffe000000, next alignment: 0x4000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffffc000000, next alignment: 0x8000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffff8000000, next alignment: 0x1000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xfffffffff0000000, next alignment: 0x2000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffe0000000, next alignment: 0x4000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffffc0000000, next alignment: 0x8000000
(gem_exec_alignment:1223) DEBUG: starting offset: 0xffffffff80000000, next alignment: 0x1000000
(gem_exec_alignment:1223) CRITICAL: Test assertion failure function single, file gem_exec_align
(gem_exec_alignment:1223) CRITICAL: Failed assertion: execobj.offset % execobj.alignment == 0
(gem_exec_alignment:1223) CRITICAL: error: 0xfffff000 != 0
****  END  ****




Used the below Configuration

Kernel
=================================================================
Branch           : drm-intel-nightly WW42 
commit 15dfed2b90e84e7c277f81842fc3f19355293061
Author: Lyude <thatslyude@gmail.com>
Date:   Sun Oct 16 19:16:08 2016 -0400

    drm-intel-nightly: 2016y-10m-16d-23h-15m-00s UTC integration manifest


Gfx stack
=================================================================
Component         : drm
        tag       : libdrm-2.4.71
        commit    : a44c9c31b7b38b3eedf3d26648f9e68dcc377c4c 

Component         : cairo
        tag       : 1.15.2
        commit    : db8a7f1697c49ae4942d2aa49eed52dd73dd9c7a 

Component         : intel-gpu-tools
        tag       : intel-gpu-tools-1.16-83-g54f8a3f
        commit    : 54f8a3f7cf12eea484a0b0641718ced559959f53
Comment 1 Jairo Miramontes 2016-10-20 22:40:34 UTC 
Test was passing under the following nightly commit: 

commit f35ed31aea66b3230c366fcba5f3456ae2cb956e
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Mon Oct 10 14:29:09 2016 +0300

    drm-intel-nightly: 2016y-10m-10d-11h-28m-51s UTC integration manifest


Will perform bisection and publish findings soon.
Comment 2 Chris Wilson 2016-10-20 22:45:41 UTC 
No need. This test was written to demonstrate a bug since inception of drm_mm.
Comment 3 Chris Wilson 2016-10-22 09:50:16 UTC 

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

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.