Bug 92501

Summary: [BYT] gem_tiled_partial_pwrite_pread/reads is failing, test assertion
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: BYT i915 features: GEM/Other
Attachments:
Description Flags
Dmesg logs none

Description Elio 2015-10-16 15:36:05 UTC 
Created attachment 118923 [details]
Dmesg logs

gem_tiled_partial_pwrite_pread@reads
Test is having 40 instead of 41 (expected value)

Configuration:


Kernel: http://vanaheimr.fr.intel.com/shared/out/kernels/drm-intel/WW42.1_4.3.0-rc4_c38f2c2/
 xorg-server-1.17.2
libdrm-2.4.65
xf86-video-intel2.99.917
mesa-11.0.2
libva-1.6.1
intel-driver 1.6.1
cairo 1.14.2
intel-gpu-tools-1.12

Hardware:
Toshiba S c55t-A Celeron 2.13 GHz, 40 Ram, HD: 500 GB

Spected result:

Test should pass 

Actual result:
Returncode	99
Time	0:00:00.983895
Stdout	
IGT-Version: 1.12-g1f9e055 (x86_64) (Linux: 4.3.0-rc4-drm-intel-testing-2015-10-10-ww41+ x86_64)
Stack trace:
  #0 [__igt_fail_assert+0xf1]
  #1 [__real_main252+0x449]
  #2 [main+0x29]
  #3 [__libc_start_main+0xf5]
  #4 [_start+0x29]
  #5 [<unknown>+0x29]
Subtest reads: FAIL (0.719s)
Stderr	
Test assertion failure function test_partial_reads, file gem_tiled_partial_pwrite_pread.c:144:
Failed assertion: tmp[j] == val
Last errno: 25, Inappropriate ioctl for device
mismatch at 90112, got: 40, expected: 41
Subtest reads failed.
**** DEBUG ****
Test assertion failure function test_partial_reads, file gem_tiled_partial_pwrite_pread.c:144:
Failed assertion: tmp[j] == val
Last errno: 25, Inappropriate ioctl for device
mismatch at 90112, got: 40, expected: 41
****  END  ****
Comment 1 Chris Wilson 2016-04-10 18:13:50 UTC 

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

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.