Bug 68830 - [Bisected]igt/gem_concurrent_blit/cpu-early-read-forked fails
Summary: [Bisected]igt/gem_concurrent_blit/cpu-early-read-forked fails
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Daniel Vetter
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-02 02:49 UTC by lu hua
Modified: 2017-10-06 14:43 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


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

Description lu hua 2013-09-02 02:49:25 UTC
Created attachment 85036 [details]
dmesg

System Environment:
--------------------------
Platform:  PNV/ILK/SNB/IVB/HSW
Kernel:    (drm-intel-nightly)4508e539b642ff40ad57f3ab7721ed2862da2eb5

Bug detailed description:
-----------------------------
It fails on PNV/ILK/SNB/IVB/HSW.It happens on drm-intel-nightly, drm-intel-next-queued, drm-intel-fixes kernel.
Following cases also fail:
igt/gem_concurrent_blit/cpu-gpu-read-after-write-forked	
igt/gem_concurrent_blit/cpu-overwrite-source-forked	
igt/gem_concurrent_blit/gtt-early-read-forked	
igt/gem_concurrent_blit/gtt-gpu-read-after-write-forked	
igt/gem_concurrent_blit/gtt-overwrite-source-forked	
igt/gem_concurrent_blit/prw-early-read-forked	
igt/gem_concurrent_blit/prw-gpu-read-after-write-forked	
igt/gem_concurrent_blit/prw-overwrite-source-forked

Bisect shows:cd1f220847c34610ab9e07c3cf1c5a7e77284eb8 is the first bad commit
commit cd1f220847c34610ab9e07c3cf1c5a7e77284eb8
Author:     Daniel Vetter <daniel.vetter@ffwll.ch>
AuthorDate: Thu Aug 29 10:06:51 2013 +0200
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Thu Aug 29 18:18:33 2013 +0200

    lib/drmtest: extract igt_fork from gem_concurrent_blt

    Making sure that we correctly collect the exit codes from all children
    is a bit a hassle. So add another magic igt codeblock for easy forking
    and joining.

    Note that children are (currently at least) not allowed to call igt_skip.
    Add an assert to enforce this.

    v2:
    - Properly propagate the exit code.
    - Fix the segfault.
    - Add a child int and num_children paramter to the magic codeblock as
      suggested by Chris Wilson.
    - Don't dump noise into stdout when a child thread fails, the parent
      will do that for us already.

    v3: Now with some docs.

    v4: Fixup igt_waitchildren to properly reset state so it can be used
    again.

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

output:
Subtest cpu-early-read-forked: FAIL

Reproduce steps:
----------------------------
1. ./gem_concurrent_blit --run-subtest cpu-early-read-forked
Comment 1 Daniel Vetter 2013-09-02 07:26:05 UTC
commit 8eaa0982d02e13d7d8d1e1a4601bbeb8adb531ae
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Mon Sep 2 08:04:19 2013 +0200

    test/gem_concurrent_blt: remove hack for testing igt_fork
    
    Oops, this shouldn't have been committed ...
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=68830
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Comment 2 lu hua 2013-09-03 02:35:36 UTC
Verified.Fixed.
Comment 3 Elizabeth 2017-10-06 14:43:32 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.