Bug 69868 - [Bisected]igt/kms_render/gpu_blit aborted
Summary: [Bisected]igt/kms_render/gpu_blit aborted
Status: CLOSED NOTABUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-27 02:36 UTC by lu hua
Modified: 2015-05-13 07:57 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (55.23 KB, text/plain)
2013-09-27 02:36 UTC, lu hua
no flags Details

Description lu hua 2013-09-27 02:36:38 UTC
Created attachment 86702 [details]
dmesg

System Environment:
--------------------------
Platform:  PNV/ILK/SNB/IVB/HSW
Kernel: (drm-intel-fixes)d32270460fee83e22ee9e6b1bfd7b486263eeb1d

Bug detailed description:
-----------------------------
It aborted on PNV/ILK/SNB/IVB/HSW with -fixes,-queued and -nightly kernel.

Bisect shows: a1ca8ef5b1f44845bb2d0eada0123eb35b7e0b21 is the first bad commit
commit a1ca8ef5b1f44845bb2d0eada0123eb35b7e0b21
Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Wed Aug 14 16:02:24 2013 +0200
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Wed Aug 14 16:08:00 2013 +0200

    tests: use igt_exit() consistently with subtests

    This is mostly important to get the SKIP reporting right, but I've
    found a few stragglers that wanted to get converted over to the igt
    result reporting completely.

    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

output:
kms_render: drmtest.c:978: igt_exit: Assertion `skipped_one || succeeded_one || failed_one' failed.
Aborted (core dumped)

Reproduce steps:
----------------------------
1. ./kms_render --run-subtest gpu_blit
Comment 1 Daniel Vetter 2013-09-27 07:39:39 UTC
The subtest is called gpu-blit, not gpu_blit. If you type the wrong subtest then things will fail. I could try to improve the error message a bit, with the current infrastructure that's a bit hard to do.


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.