Bug 68091 - [SNB]igt/gem_write_read_ring_switch/blt2vebox-interruptible aborted
Summary: [SNB]igt/gem_write_read_ring_switch/blt2vebox-interruptible aborted
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Daniel Vetter
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-14 06:56 UTC by lu hua
Modified: 2017-10-06 14:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg (71.73 KB, text/plain)
2013-08-14 06:56 UTC, lu hua
no flags Details

Description lu hua 2013-08-14 06:56:04 UTC
Created attachment 84043 [details]
dmesg

System Environment:
--------------------------
Platform:    Sandybridge
Kernel:      (drm-intel-nightly)b382289157092f9c7643acd1cd8640b26bbca0ab

Bug detailed description:
-----------------------------
It aborted on sandybridge with -nightly, -fixes, -queued kernel. It's a new case.

output:
running subtest blt2vebox-interruptible
intel_batchbuffer_flush_on_ring:118 failed, ret=-22, errno=0
Aborted (core dumped)

Reproduce steps:
----------------------------
1. ./gem_write_read_ring_switch --run-subtest blt2vebox-interruptible
Comment 1 Chris Wilson 2013-08-14 07:19:38 UTC
commit 4f8c9a2c386154a5be94e117b4371ab0ef8b55a8
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Wed Aug 14 08:17:22 2013 +0100

    gem_write_read_ring_switch: Copy the missing igt_require
    
    An oversight in the mass conversion to the new framework as the test was
    called from two locations.
    
    Ideally, the checks could be moved back to the caller and the framework
    still work. This is just the patch of least resistence.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=68091
Comment 2 lu hua 2013-08-14 08:30:48 UTC
Verified.Fixed by commit 4f8c9a2c386154a5be94e117b4371ab0ef8b55a8.
Comment 3 Elizabeth 2017-10-06 14:44:08 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.