Bug 77875 - [BYT/BDW Regression]igt/gem_flink_race/flink_close fails
Summary: [BYT/BDW Regression]igt/gem_flink_race/flink_close fails
Status: CLOSED DUPLICATE of bug 77867
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:
Depends on:
Blocks:
 
Reported: 2014-04-24 07:37 UTC by Guo Jinxian
Modified: 2017-07-24 22:54 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (79.00 KB, text/plain)
2014-04-24 07:37 UTC, Guo Jinxian 		no flags Details
lib/drmtest: don't open exit fds in advance (2.00 KB, patch)
2014-05-07 12:59 UTC, Mika Kuoppala 		no flags Details | Splinter Review
Show Obsolete (1) View All

Description Guo Jinxian 2014-04-24 07:37:03 UTC 
Created attachment 97878 [details]
dmesg

System Environment:
--------------------------
Platform: BYT BDW
kernel:   (drm-intel-nightly) 6c398a53417fd96d9e58bdb618e395163c81e1c4

Bug detailed description:
----------------------------
igt/gem_flink_race/flink_close fails on -nightly

It's a regression bug:
Good commit: 798fca377a0e26cffb40e5a97230baaac4b12733
Bad commit: 78e4c2b449c6d0a18e2bfaea29f3a0eadb42c5f3
We will bisect it later

output on -nightly kernel:
IGT-Version: 1.6-g78e4c2b (x86_64) (Linux: 3.15.0-rc2_drm-intel-nightly_6c398a_20140424+ x86_64)
leaked 2 objects
Test assertion failure function test_flink_close, file gem_flink_race.c:196:
Last errno: 0, Success
Failed assertion: obj_count == 0
Subtest flink_close: FAIL


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

1. ./gem_flink_race --run-subtest flink_close
Comment 1 Mika Kuoppala 2014-05-07 12:59:59 UTC 
Created attachment 98621 [details] [review]
lib/drmtest: don't open exit fds in advance
Comment 2 Mika Kuoppala 2014-05-07 13:10:46 UTC 

*** This bug has been marked as a duplicate of bug 77867 ***

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.