Bug 59096

Summary: [SNB]I-G-T/gem_render_linear_blits & gem_render_tiled_blits fail
Product: DRI Reporter: yanbing <bingx.a.yan>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: bingx.a.yan
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
gem_render.dmesg none

Description yanbing 2013-01-07 03:50:12 UTC 
Created attachment 72607 [details]
gem_render.dmesg

Environment:
--------------------------
Kernel: (drm-intel-next-queued)c0c36b941b6f0be6ac74f340040cbb29d6a0b06c
Some additional commit info:
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Dec 19 16:08:43 2012 +0000

    drm/i915: Return the real error code from intel_set_mode()


Steps:
---------------------------

1 ./gem_render_linear_blits
2 ./gem_render_tiled_blits


Result:
--------------------------
1.Using 3069 1MiB buffers
  Verifying initialisation...
  Cyclic blits, forward...
  Expected 0x00000001, found 0x00000000 at offset 0x00000004
  Aborted (core dumped)
2.$?=134
3.Using 3069 1MiB buffers
  Verifying initialisation...
  Expected 0x24347100, found 0xe96caa55 at offset 0x0001c400
  Aborted (core dumped)
4.$?=134
5.gem_render.dmesg in the attachment
6 [review].I can't find a good commit on the next_queue branch.
Comment 1 Daniel Vetter 2013-01-24 09:43:32 UTC 
I've just tested this on my snb with latest i-g-t and -nightly kernel, both pass. Can you please retest?
Comment 2 yanbing 2013-01-25 01:59:02 UTC 
(In reply to comment #1)
> I've just tested this on my snb with latest i-g-t and -nightly kernel, both
> pass. Can you please retest?

ok，I retest both with latest -nightly on SNB,both pass.
So we can close this bug now.
Comment 3 Elizabeth 2017-10-06 14:47:16 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.