Bug 89596 - [SKL]System output "ERROR" when it resumes from S4 connecting DP monitor.
Summary: [SKL]System output "ERROR" when it resumes from S4 connecting DP monitor.
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-16 14:56 UTC by liulei
Modified: 2017-10-06 14:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (361.75 KB, text/plain)
2015-03-16 14:56 UTC, liulei 		no flags Details
View All

Description liulei 2015-03-16 14:56:10 UTC 
Created attachment 114350 [details]
dmesg

==System Environment==
--------------------------
Regression: No. This is the first time to test this case on SKL.
Non-working platforms: SKL

Connecting monitors: 
eDP, DP(Dell UP32140Qt), HDMI

==kernel==
--------------------------
-nightly: f7def439e21cacf7656539edc55a4884734743de (fails)

==Bug detailed description==
-----------------------------
System output "ERROR"  when it resumes from S4 with 3 pipe.

ERROR:
[drm:intel_dp_set_signal_levels] Using signal levels 07000000
[drm:intel_dp_set_signal_levels] Using signal levels 09000000
[drm:intel_dp_start_link_train [i915]] *ERROR* too many full retries, give up
[drm:intel_dp_set_signal_levels] Using signal levels 09000000
[drm:intel_dp_set_signal_levels] Using signal levels 09000000


==Reproduce steps==
---------------------------- 
1. connect 3 monitor in total(eDP, DP, HDMI).
2. do S4
Comment 1 liulei 2015-03-17 03:18:15 UTC 
System will also output ERROR with only connecting DP monitor
Comment 2 liulei 2015-03-17 03:19:42 UTC 
(In reply to liulei from comment #1)
> System will also output ERROR with only connecting DP monitor
I mean:
System output "ERROR" when it resumes from S4 with connecting DP monitor.
Comment 3 Damien Lespiau 2015-05-21 16:58:56 UTC 
The cause should be because we didn't reinitialize the display and so the AUX transactions for the link training were failing. The driver has a lot more chances to work now (survived a few S4 cycles here).
Comment 4 ye.tian 2015-05-22 01:48:40 UTC 
Test it on the latest nightly kernel(790a30), this problem doest not exists.
So verified.
Comment 5 Elizabeth 2017-10-06 14:31:01 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.