Bug 89077 - [BSW]igt/gem_concurrent_blit/cpu-gtt-gpu-read-after-write-forked takes more than 10 minutes
Summary: [BSW]igt/gem_concurrent_blit/cpu-gtt-gpu-read-after-write-forked takes more t...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-11 07:25 UTC by lu hua
Modified: 2017-07-24 22:48 UTC (History)
2 users (show)

See Also:
i915 platform: BSW/CHT
i915 features: GEM/Other


Attachments
dmesg (124.82 KB, text/plain)
2015-02-11 07:25 UTC, lu hua
no flags Details

Description lu hua 2015-02-11 07:25:37 UTC
Created attachment 113338 [details]
dmesg

==System Environment==
--------------------------
Regression: not sure

no-working platforms: BSW

==kernel==
--------------------------
drm-intel-nightly/ad95125eaef18eebb9f47261ce3c99957f5953de
commit ad95125eaef18eebb9f47261ce3c99957f5953de
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Mon Feb 9 21:31:04 2015 +0100

    drm-intel-nightly: 2015y-02m-09d-20h-26m-16s UTC integration manifest

==Bug detailed description==
It takes more than 10 minutes. We test full gem_concurrent_blit the first round on BSW since 160 new subcase merged.
Following cases also take more than 10 minutes:
igt/gem_concurrent_blit/cpu-gtt-gpu-read-after-write-interruptible
igt/gem_concurrent_blit/gpu-gtt-gpu-read-after-write-interruptible
igt/gem_concurrent_blit/gpuX-gtt-gpu-read-after-write-forked
igt/gem_concurrent_blit/gpuX-gtt-gpu-read-after-write-interruptible
igt/gem_concurrent_blit/gtt-gtt-gpu-read-after-write-interruptible


IGT-Version: 1.9-g9846e7f (x86_64) (Linux: 3.19.0_drm-intel-nightly_34f9b9_20150211+ x86_64)
using 2x512 buffers, each 1MiB
Subtest cpu-gtt-gpu-read-after-write-forked: SUCCESS (517.509s)

real    10m51.817s
user    34m2.487s
sys     2m40.405s

==Reproduce steps==
---------------------------- 
1. time ./gem_concurrent_blit --run-subtest cpu-gtt-gpu-read-after-write-forked
Comment 1 lu hua 2015-02-11 07:46:24 UTC
gpu-gtt-gpu-read-after-write-forked also takes more than 10 minutes
root@x-bsw06:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time ./gem_concurrent_blit --run-subtest gpu-gtt-gpu-read-after-write-forked
IGT-Version: 1.9-g9846e7f (x86_64) (Linux: 3.19.0_drm-intel-nightly_34f9b9_20150211+ x86_64)
using 2x512 buffers, each 1MiB
Subtest gpu-gtt-gpu-read-after-write-forked: SUCCESS (595.237s)

real    12m11.088s
user    38m56.643s
sys     2m45.936s
Comment 2 lu hua 2015-02-12 02:27:11 UTC
Following cases also take more than 10 minutes.
igt/gem_concurrent_blit/gttX-gtt-gpu-read-after-write-forked
igt/gem_concurrent_blit/gttX-gtt-gpu-read-after-write-interruptible
igt/gem_concurrent_blit/prw-gtt-gpu-read-after-write-interruptible
igt/gem_concurrent_blit/wc-gtt-gpu-read-after-write-forked
igt/gem_concurrent_blit/wc-gtt-gpu-read-after-write-interruptible
Comment 3 lu hua 2015-02-12 06:05:45 UTC
igt/gem_concurrent_blit/prw-gtt-gpu-read-after-write-forked also takes more than 10 minutes.
Comment 4 Jani Nikula 2015-10-28 19:03:00 UTC
Timeout, closing. Please reopen if the problem persists with latest kernels.


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.