Bug 92700

Summary: [BDW] IGT gem_pwrite_snooped fails
Product: DRI Reporter: Elio <elio.martinez.monroy>
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: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Dmesg log none

Description Elio 2015-10-27 21:44:35 UTC
Created attachment 119234 [details]
Dmesg log

Returncode	99
Time	0:00:00.029627
Stdout	
IGT-Version: 1.12-g1f9e055 (x86_64) (Linux: 4.3.0-rc6-mainline+ x86_64)
Stack trace:
  #0 [__igt_fail_assert+0xf1]
  #1 [main+0x306]
  #2 [__libc_start_main+0xf5]
  #3 [_start+0x29]
  #4 [<unknown>+0x29]
FAIL (0.004s)
Stderr	
Test assertion failure function test, file gem_pwrite_snooped.c:125:
Failed assertion: memchr_inv(buf, 0xff, object_size) == NULL
Test gem_pwrite_snooped failed.
**** DEBUG ****
(gem_pwrite_snooped:2265) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation()
Test requirement passed: fd >= 0
Test requirement passed: ret == 0
Test requirement passed: ret == 0
Test assertion failure function test, file gem_pwrite_snooped.c:125:
Failed assertion: memchr_inv(buf, 0xff, object_size) == NULL
****  END  ****

Steps to reproduce:

Install Graphics stack with test eviroment configuration. 
Execute: ./run-test.sh -t gem_pwrite_snooped

Expected result: test should pass

Actual result: test fails


Test Enviroment:


kernel: 4.3.0-rc6-drm-intel-nightly
xorg-server-1.17.2
libdrm-2.4.65
xf86-video-intel-2.99.917
mesa-11.0.4-devel 
libva-1.6.1
intel-driver-1.6.1
cairo-1.14.2


Platform:
Broadwell-U
Hardware
Platform: Lenovo G50
Processor: Intel Core I5-5200 2.20 GHz
Software
Linux distribution: Ubuntu 14.04.03 LTS 64 bits
BIOS:B0CN69WW
Comment 1 Chris Wilson 2015-10-28 09:40:38 UTC

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

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.