[Bug 77875] New: [BYT/BDW Regression]igt/gem_flink_race/flink_close fails

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Apr 24 00:37:03 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=77875

          Priority: medium
            Bug ID: 77875
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: [BYT/BDW Regression]igt/gem_flink_race/flink_close
                    fails
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: jinxianx.guo at intel.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

Created attachment 97878
  --> https://bugs.freedesktop.org/attachment.cgi?id=97878&action=edit
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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140424/38bcab9d/attachment.html>


More information about the intel-gfx-bugs mailing list