Bug 97638 - [SKL] [i915] External monitor does not wake up but laptop screen does (USB-C -> DisplayPort)
Summary: [SKL] [i915] External monitor does not wake up but laptop screen does (USB-C ...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: high normal
Assignee: Clinton Taylor
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-08 13:31 UTC by Victor Trac
Modified: 2017-07-20 22:37 UTC (History)
2 users (show)

See Also:
i915 platform: SKL
i915 features: display/DP


Attachments
dmesg (92.56 KB, text/x-log)
2016-09-08 13:31 UTC, Victor Trac
no flags Details
journalctl -f log output (19.45 KB, text/plain)
2016-09-08 13:32 UTC, Victor Trac
no flags Details

Description Victor Trac 2016-09-08 13:31:52 UTC
Created attachment 126304 [details]
dmesg

-- system architecture: x86_64
-- kernel version: ("uname -r"). 4.8.0-1-drm-intel-nightly
-- Linux distribution: archlinux
-- Machine or mother board model: Dell XPS 13 9350
-- Display connector: usb-c -> kensington sd4600p -> displayport -> dell P2715q

Problem:
My laptop turns off displays (both internal and external) after 10 minutes. When I move the mouse or keyboard, the laptop display turns on as expected, but the external monitor stays in sleep mode. Based on what's displaying on my laptop's screen, I can tell that GDM is showing the login window on what it thinks is the external monitor. I can get the external monitor to work at this point by power cycling the Dell P2715Q, which causes it to detect the DP Input. At this point everything works fine until the next time the laptop turns off the displays.
Comment 1 Victor Trac 2016-09-08 13:32:46 UTC
Created attachment 126305 [details]
journalctl -f log output
Comment 2 Victor Trac 2016-10-14 18:36:57 UTC
Still happening on the latest drm-intel nightlies.  I have to disconnect usb-c or power-cycle my monitor to get my laptop to send input to the external display over displayport.
Comment 3 anusha 2017-03-16 00:11:52 UTC
Hi,

Can you tell your finding with a newer kernel?
Comment 4 Victor Trac 2017-03-16 03:33:45 UTC
Still happening on 4.10.0-1-drm-intel-nightly (built on Feb 21). It's been a fairly stable kernel for me, so I've been hesitant to update since then.

It might very well be my Kensington SD4600P USB-C dock.
Comment 5 Ryan 2017-04-12 08:06:20 UTC
Hi Victor,

I was having the same problem on the Kensington SD4600P dock.

On HDMI the screens would come back if I moved the mouse
on Display Port the DP screen would not wake up unless I powered it off an on again.

I am using windows 10. 


I upgraded the firmware of the dock ----> 

https://accoblobstorageus.blob.core.windows.net/software/cda1cf8e-d0ae-4611-94df-0a59d60e3f1c.zip


Which is a link from Kensingtons website here: 
https://www.kensington.com/us/us/3693/software-drivers

It looks like that has solved the problem.

So I would say that it is certainly the dock that is the issue and hopefully the firmware works for you.
Comment 6 Jani Nikula 2017-04-12 09:22:59 UTC
Please try current drm-tip branch of https://cgit.freedesktop.org/drm/drm-tip that has

commit 9a86cda07af2c63649932f0a4fc757701ef54c42
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Mon Mar 27 14:33:25 2017 +0300

    drm/i915/dp: reduce link M/N parameters
Comment 7 Victor Trac 2017-04-29 16:05:12 UTC
@ryan Thanks - I check the kensington site religious for firmware updates for the sd4600p and have been running that firmware since release.

@jani - I have to run drm-intel nightlies for other reasons, which I think should incorporate the changes in drm-tip, correct?  I'll build another kernel and see if I can reproduce.
Comment 8 Jari Tahvanainen 2017-05-23 15:53:06 UTC
Victor - any news?
Comment 9 Ricardo 2017-07-20 22:37:22 UTC
based on the lack of activity this bug will be closed... please if the problem is reproducible with latest configuration open a new bug including logs.


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.