Bug 48026

Summary: [Regression]I-G-T/gem_linear_blits fail
Product: DRI Reporter: Guang Yang <guang.a.yang>
Component: DRM/IntelAssignee: Daniel Vetter <daniel>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: medium CC: ben, chris, daniel, jbarnes
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 40928    

Description Guang Yang 2012-03-29 01:08:04 UTC 
System Environment:
--------------------------
Platform:        Pineview/Sandybridge/Ivbridge
Kernel: (drm-intel-next-queued)e7e58eb5c0d1d7d1a42fcb2b5a247d28ec08b47e
Bug detailed description:
-------------------------
   On PNV/SNB/IVB platform ,running gem_linear_blits of the
Intel-gpu-tools will fail.

  the error on the console is like this:
   not enough RAM to run test, reducing buffer count
   Using 2432 1MiB buffers
   Verifying initialisation...
   Cyclic blits, forward...
   Expected 0x00000000, found 0x13380000 at offset 0x00000000
   Aborted (core dumped)

   Here is the GDB backtrace:
#0  0xb7fff424 in __kernel_vsyscall ()
#1  0x48ab6d71 in raise () from /lib/libc.so.6
#2  0x48ab864a in abort () from /lib/libc.so.6
#3  0x0804927f in check_bo (fd=<value optimized out>, handle=<value optimized   out>, val=<value optimized out>) at gem_linear_blits.c:172
#4  0x080494da in main (argc=1, argv=0xbffff0d4) at gem_linear_blits.c:221

   Here is a good kernel commit:
Kernel: (drm-intel-next-queued)1d83f4426fa0555c98c989915be6df01a8125aca
   If have a demand,I can bisect it.
Comment 1 Daniel Vetter 2012-03-30 13:02:35 UTC 
This should be fixed by the following patch from -fixes:

commit 5d031e5b633d910f35e6e0abce94d9d842390006
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Feb 8 13:34:13 2012 +0000

    drm/i915: Remove use of the autoreported ringbuffer HEAD position
Comment 2 Guang Yang 2012-03-30 19:12:10 UTC 
 confirmed, the bug has been fixed with -fixes branch.
Comment 3 Elizabeth 2017-10-06 14:50:40 UTC 
Closing old verified.

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.