Bug 105175 - Blank screens [drm:intel_mst_enable_dp [i915]] *ERROR* Timed out waiting for ACT sent
Summary: Blank screens [drm:intel_mst_enable_dp [i915]] *ERROR* Timed out waiting for ...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-20 17:01 UTC by Stef
Modified: 2018-04-03 10:25 UTC (History)
3 users (show)

See Also:
i915 platform: KBL, SKL
i915 features: display/backlight


Attachments
4.15.4 log (424.88 KB, text/x-log)
2018-02-20 17:01 UTC, Stef
no flags Details
4.14.20 log (259.54 KB, text/x-log)
2018-02-20 17:01 UTC, Stef
no flags Details

Description Stef 2018-02-20 17:01:05 UTC
Created attachment 137470 [details]
4.15.4 log

ThinkPad X1 Carbon 4th Gen running i7-6600u Skylake

Displays connected to ThinkPad OneLink Plus Dock work in bios/grub and on kernel version 4.14.20, but fail to light up on kernel 4.15.4

drm.debug=0xe logs attached

available firmwares:
/lib/firmware/i915/skl_huc_ver01_07_1398.bin
/lib/firmware/i915/skl_guc_ver9_33.bin
/lib/firmware/i915/skl_guc_ver6_1.bin
/lib/firmware/i915/skl_dmc_ver1_26.bin
Comment 1 Stef 2018-02-20 17:01:39 UTC
Created attachment 137471 [details]
4.14.20 log
Comment 2 Werner Gold 2018-02-21 08:21:44 UTC
Same error, when booting the T460S with the latest kernel update.

VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)

kernel-4.15.3-300.fc27.x86_64
Comment 3 Pawel Kurdybacha 2018-02-21 09:45:36 UTC
Same error here as well on T470 with the latest kernel update on Fedora.

kernel-4.15.3-300.fc27.x86_64
VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02
Comment 4 frederik 2018-03-18 16:31:08 UTC
Had a similar problem. I applied this patch [0] and the blank screens eventually turned on after boot (takes about 30s - don't know why).
Probably worth a try.

[0] https://patchwork.freedesktop.org/patch/210500/
Comment 5 Jani Saarinen 2018-03-29 07:11:37 UTC
First of all. Sorry about spam.
This is mass update for our bugs. 

Sorry if you feel this annoying but with this trying to understand if bug still valid or not.
If bug investigation still in progress, please ignore this and I apologize!

If you think this is not anymore valid, please comment to the bug that can be closed.
If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Comment 6 Stef 2018-03-29 15:33:21 UTC
(In reply to Jani Saarinen from comment #5)
> First of all. Sorry about spam.
> This is mass update for our bugs. 
> 
> Sorry if you feel this annoying but with this trying to understand if bug
> still valid or not.
> If bug investigation still in progress, please ignore this and I apologize!
> 
> If you think this is not anymore valid, please comment to the bug that can
> be closed.
> If you haven't tested with our latest pre-upstream tree(drm-tip), can you do
> that also to see if issue is valid there still and if you cannot see issue
> there, please comment to the bug.

I just checked the latest kernels again:
4.14.31 - still working
4.15.14 - still failing
4.16-rc7 - working again!

I don't know how to track which drm-tip commits made it into mainline kernel, but seems like the fix needs to be committed to the 4.15 stable branch.
Comment 7 Elizabeth 2018-04-02 20:30:43 UTC
Thank you for the update. I'm closing then, if problem returns please mark as REOPEN.


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.