Bug 77867 - [All Bisected]Subcases reimport-vs-gem_close-race and export-vs-gem_close-race of prime_self_import fail
Summary: [All Bisected]Subcases reimport-vs-gem_close-race and export-vs-gem_close-rac...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Mika Kuoppala
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 77421 77875 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-04-24 06:18 UTC by Guo Jinxian
Modified: 2017-10-06 14:38 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (123.23 KB, text/plain)
2014-04-24 06:18 UTC, Guo Jinxian 		no flags Details
lib/drmtest: don't open exit fds in advance (2.00 KB, patch)
2014-05-07 13:10 UTC, Mika Kuoppala 		no flags Details | Splinter Review
tests/gem_flink_race,prime_self_import: fix object counts (1.94 KB, patch)
2014-05-07 13:52 UTC, Mika Kuoppala 		no flags Details | Splinter Review
Show Obsolete (1) View All

Description Guo Jinxian 2014-04-24 06:18:06 UTC 
Created attachment 97871 [details]
dmesg

System Environment:
--------------------------
Platform: All
kernel:   (drm-intel-nightly)35dc7c8af75a3e5ae52a5469786602ce083a6368
Intel-gpu-tools: 78e4c2b449c6d0a18e2bfaea29f3a0eadb42c5f3

Bug detailed description:
----------------------------
Subcases reimport-vs-gem_close-race and export-vs-gem_close-race of prime_self_import fail

It's a regression bug about igt:
good commit: f74c443925578b377c47d655a2d864b8ed521330
bad commit: 78e4c2b449c6d0a18e2bfaea29f3a0eadb42c5f3
We will bisect it later

output on -next-queued kernel:
./prime_self_import --run-subtest reimport-vs-gem_close-race
IGT-Version: 1.6-g78e4c2b (x86_64) (Linux: 3.14.0_drm-intel-next-queued_f68918_20140424+ x86_64)
leaked 1 objects
Test assertion failure function test_reimport_close_race, file prime_self_import.c:297:
Last errno: 0, Success
Failed assertion: obj_count == 0
Subtest reimport-vs-gem_close-race: FAIL

Reproduce steps:
---------------------------- 

1. ./prime_self_import --run-subtest export-vs-gem_close-race
   or 
   ./prime_self_import --run-subtest reimport-vs-gem_close-race
Comment 1 Daniel Vetter 2014-04-28 13:18:07 UTC 
Can you please bisect and check whether this is a dupe of bug #77421

We should probably close the other bug then and mark it as a dupe of this one here.
Comment 2 Guo Jinxian 2014-04-29 06:32:24 UTC 
2f2c491cf3167befe7c79e4b17afb4f6284dfc84 is the first bad commit
commit 2f2c491cf3167befe7c79e4b17afb4f6284dfc84
Author:     Mika Kuoppala <mika.kuoppala@intel.com>
AuthorDate: Fri Mar 28 10:52:46 2014 +0200
Commit:     Mika Kuoppala <mika.kuoppala@intel.com>
CommitDate: Thu Apr 10 17:50:49 2014 +0300

    lib/drmtest: don't dup quiescent fd

    If we dup the fd, we are in mercy of the context banning
    of the test application. Better to have our own to guarantee
    that gem_quiescent_gpu won't find itself banned on exit.

    Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>

:040000 040000 ceeb48448f495672745b61fb7e7a61f151f26cc5 4dddf6d79c79df33d39e193bcf81898b149d6973 M      lib


reverted the commit, the test result was passed.

It is a dupe of bug #77421, I will close bug 77421 as duplicate, Thanks.
Comment 3 Guo Jinxian 2014-04-29 06:33:16 UTC 
*** Bug 77421 has been marked as a duplicate of this bug. ***
Comment 4 Mika Kuoppala 2014-05-07 13:10:18 UTC 
Created attachment 98622 [details] [review]
lib/drmtest: don't open exit fds in advance
Comment 5 Mika Kuoppala 2014-05-07 13:10:46 UTC 
*** Bug 77875 has been marked as a duplicate of this bug. ***
Comment 6 Mika Kuoppala 2014-05-07 13:52:37 UTC 
Created attachment 98626 [details] [review]
tests/gem_flink_race,prime_self_import: fix object counts
Comment 7 Mika Kuoppala 2014-05-07 14:48:18 UTC 
fix pushed to igt
Comment 8 Guo Jinxian 2014-05-15 05:42:26 UTC 
Fixes on latest igt(351e7d395041b4b87ad28a201c81acac40cb397f), Thanks.
Comment 9 Elizabeth 2017-10-06 14:38:33 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.