Bug 72751

Summary: [BYT]Flicker screen shows on HDMI output while testing testdisplay -f 38.25,800,832,912,1024,600,603,607,624
Product: DRI Reporter: Guo Jinxian <jinxianx.guo>
Component: DRM/IntelAssignee: Ville Syrjala <ville.syrjala>
Status: CLOSED FIXED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description Guo Jinxian 2013-12-16 09:48:55 UTC 
Environment:
--------------------------
Kernel: drm-intel-testing
commit 95d42e7d341861132ffec806328dd7fc85516995
Merge: cf8f3ba 2a0a016
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Dec 13 17:57:43 2013 +0100

    Merge remote-tracking branch 'origin/topic/core-stuff' into drm-intel-nightly

Bug detailed description:
-----------------------------
Flicker screen while testing testdisplay -f 38.25,800,832,912,1024,600,603,607,624
It occurs on 1 machine(total test on 3 machines).It's first time to run display test on this machine.

The testing runs on 2 pipe mode(VGA+HDMI) and the flicker screen shows on HDMI screen. If only pluged HDMI, flicker screen will doesn't shown.

Steps:
---------------------------
./testdisplay -f 38.25,800,832,912,1024,600,603,607,624
Comment 1 Guo Jinxian 2013-12-17 00:56:21 UTC 
Created attachment 90851 [details]
dmesg
Comment 2 Guo Jinxian 2013-12-17 01:22:30 UTC 
Here is video link: http://youtu.be/NXzOA9Ye208, thanks.
Comment 3 Daniel Vetter 2013-12-17 09:24:45 UTC 
That looks very much like pipe underruns. Unfortunately we don't have pipe underrun reporting enabled on byt, so can't say for sure using debug logs :(
Comment 4 Chris Wilson 2014-01-27 11:59:32 UTC 
Ville, did your watermark changes include byt?

Anyway worth retesting with that series now in -nightly.
Comment 5 Ville Syrjala 2014-01-27 12:49:55 UTC 
(In reply to comment #4)
> Ville, did your watermark changes include byt?

Nope, watermark changes are limited to pch platforms for now.
Comment 6 Guo Jinxian 2014-01-28 02:34:48 UTC 
(In reply to comment #4)

> Anyway worth retesting with that series now in -nightly.

This bug unable to reproduce on latest -nightly(9438dec1c7538fdd3b356a59ca929632fcb57132). Thanks.
Comment 7 zhoujian 2014-03-24 02:17:33 UTC 
The problem also exist on DP output.
Comment 8 Daniel Vetter 2014-03-26 21:21:07 UTC 
Please explain what's going on here. Comment #6 says -nightly works, comment #7 says dp is also broken (so -nightly is probably broken).

Can we close this or is this still an issue on -nightly?
Comment 9 Guo Jinxian 2014-03-27 07:26:33 UTC 
(In reply to comment #8)
> Please explain what's going on here. Comment #6 says -nightly works, comment
> #7 says dp is also broken (so -nightly is probably broken).
> 
> Can we close this or is this still an issue on -nightly?

Comment #6 was tested on -nightly, Comment #7 was the test result on 2014Q1 resease, maybe the patch didn't include into 2014Q1 release.


I checked on latest -nightly(e5ad48d0d4f08e5db537901a2d7b2f0750ddd88c), This bug  unable to reproduce.
Comment 10 Daniel Vetter 2014-03-27 08:33:31 UTC 
Yeah, hdmi compliance is still a bit busted. I guess until we have a customer complaint we can just close this and ignore the missing backported patch.
Comment 11 Guo Jinxian 2014-03-28 01:06:07 UTC 
Verified according the latest -nightly(e5ad48d0d4f08e5db537901a2d7b2f0750ddd88c) result
Comment 12 Elizabeth 2017-10-06 14:41:19 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.