Bug 82230

Summary: [SNB/IVB/BDW/BSW]igt/kms_force_connector fails
Product: DRI Reporter: Guo Jinxian <jinxianx.guo>
Component: DRM/IntelAssignee: Thomas Wood <thomas.wood>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description Guo Jinxian 2014-08-06 07:50:13 UTC
Created attachment 104137 [details]
dmesg

==System Environment==
--------------------------
Regression: No. 
It's new case

Non-working platforms: SNB

==kernel==
--------------------------
origin/drm-intel-nightly: 79e44bfa10063ee529140e88fdc401c4ce07d644(fails)
    drm-intel-nightly: 2014y-08m-06d-00h-42m-38s integration manifest
origin/drm-intel-next-queued: 414863f8733f79e7e25283499fdede1ca987f216(fails)
    drm/i915: Don't accumulate hangcheck score on forward progress
origin/drm-intel-fixes: 96d56d71a3bcd0a0015034a8f3decc46cb9ec855(fails)
    drm/i915: Fix crash when failing to parse MIPI VBT

==Bug detailed description==
igt/kms_force_connector fails

Output:
[root@x-sgb4 tests]# ./kms_force_connector
IGT-Version: 1.7-gac31f19 (i686) (Linux: 3.16.0_drm-intel-next-queued_414863_20140806+ i686)
Test assertion failure function main, file kms_force_connector.c:100:
Failed assertion: temp->count_modes == 5


==Reproduce steps==
---------------------------- 
1. ./kms_force_connector
Comment 1 Guo Jinxian 2014-09-04 02:49:05 UTC
The failure is able to reproduce on IVB on latest -nightly(2b1159961e4bc38a9090f8ec0ab6f16701dbdf81)

[root@x-ivb9 tests]# ./kms_force_connector
IGT-Version: 1.7-gf473a55 (x86_64) (Linux: 3.17.0-rc2_drm-intel-nightly_2b1159_20140903_debug+ x86_64)
Test assertion failure function main, file kms_force_connector.c:100:
Failed assertion: temp->count_modes == 5
Comment 2 lu hua 2014-10-11 07:25:34 UTC
It also fails on BDW/BSW.
Comment 3 Damien Lespiau 2014-10-14 17:07:24 UTC
Hopefully Thomas will know the history here.
Comment 4 Thomas Wood 2014-10-15 10:30:30 UTC
Is the VGA output connected when the test is run?
Comment 5 Guo Jinxian 2014-10-16 07:04:00 UTC
(In reply to Thomas Wood from comment #4)
> Is the VGA output connected when the test is run?

No, most devices are eDP output.

The failure changed on latest -nightly

[root@x-bsw01 tests]# ./kms_force_connector
IGT-Version: 1.8-ga0b5c6d (x86_64) (Linux: 3.17.0_drm-intel-nightly_2ea23c_20141016+ x86_64)
Test assertion failure function main, file kms_force_connector.c:57:
Failed assertion: connector

root@x-bdw05:~# cd /GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests/
root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./kms_force_connector
IGT-Version: 1.8-ga0b5c6d (x86_64) (Linux: 3.17.0_drm-intel-nightly_2ea23c_20141016+ x86_64)
Test assertion failure function main, file kms_force_connector.c:57:
Failed assertion: connector
Comment 6 Thomas Wood 2014-10-16 09:37:32 UTC
(In reply to Guo Jinxian from comment #5)
> (In reply to Thomas Wood from comment #4)
> > Is the VGA output connected when the test is run?
> 
> No, most devices are eDP output.
> 
> The failure changed on latest -nightly
> 
> [root@x-bsw01 tests]# ./kms_force_connector
> IGT-Version: 1.8-ga0b5c6d (x86_64) (Linux:
> 3.17.0_drm-intel-nightly_2ea23c_20141016+ x86_64)
> Test assertion failure function main, file kms_force_connector.c:57:
> Failed assertion: connector
> 
> root@x-bdw05:~# cd /GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests/
> root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests#
> ./kms_force_connector
> IGT-Version: 1.8-ga0b5c6d (x86_64) (Linux:
> 3.17.0_drm-intel-nightly_2ea23c_20141016+ x86_64)
> Test assertion failure function main, file kms_force_connector.c:57:
> Failed assertion: connector

This is a different error from the one originally reported. Can you still reproduce the original issue? The issue above is already fixed by commit e11b710 (tests/kms_force_connect: skip if a VGA connector is not available).
Comment 7 Thomas Wood 2014-10-16 09:53:02 UTC
If the original issue can still be reproduced, please retest with this patch: http://patchwork.freedesktop.org/patch/35120/
Comment 8 Thomas Wood 2014-10-17 15:02:44 UTC
(In reply to Thomas Wood from comment #7)
> If the original issue can still be reproduced, please retest with this
> patch: http://patchwork.freedesktop.org/patch/35120/

The above patch has now been merged, so both issues mentioned in the bug should now be fixed.
Comment 9 Guo Jinxian 2014-10-21 07:41:49 UTC
(In reply to Thomas Wood from comment #8)
> (In reply to Thomas Wood from comment #7)
> > If the original issue can still be reproduced, please retest with this
> > patch: http://patchwork.freedesktop.org/patch/35120/
> 
> The above patch has now been merged, so both issues mentioned in the bug
> should now be fixed.

This failure unable to reproduce. but here has another bug 85279. Verify this one.
Comment 10 Elizabeth 2017-10-06 14:36:47 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.