Description of problem: After un-docking and later re-docking the laptop, both displays blank and I have to hard-reset. Version-Release number of selected component (if applicable): 4.11.3-200.fc25.x86_64, but I think I've also noticed this with the latest in the 4.10 series. How reproducible: Not sure if 100%. Steps to Reproduce: 1. Dock (ThinkPad Ultra Pro http://www3.lenovo.com/us/en/accessories/docking/mechanical-docks/ThinkPad-Ultra-Dock-90-W/p/40A20090US) with one external display connected over DisplayPort. 2. Boot docked, suspend/resume while on dock a couple of times during the day, finally suspend. 3. Un-dock, resume/suspend a few times while "on the road", finally suspend. 4. Re-dock, resume. Laptop display shows GNOME screensaver for a second, then goes dark. External display doesn't light up. I have to hard-reset the machine. Actual results: No display after re-docking Expected results: Used to not be an issue, as of, approximately, the early 4.10 series or 4.9 series. At worst, I had to re-arrange monitors in the GNOME display settings. Additional info:
Sorry, forgot to add: Laptop is an X250, Intel graphics only.
Reproduced today, still under 4.11.3-200.fc25.x86_64. Noticed a lot of this in the log, which doesn't seem to happen when re-docking is successful: kernel: [drm:intel_dp_set_idle_link_train [i915]] *ERROR* Timed out waiting for DP idle patterns
Had to go "on the road" again today, so tried a variation of the steps from the description: Before re-docking the suspended laptop, I disconnected the DisplayPort cable from the dock. After the laptop was docked and resumed, I re-connected the DP cable. Could not reproduce this time, and no log messages from the display driver. I'll try a few more times to confirm that the dock is not a factor.
Tried a couple times to reproduce with 4.11.4-200.fc25.x86_64, no repro yet. I'll try a few more times as workload permits.
Unfortunately I just reproduced this again under 4.11.4-200.fc25.x86_64
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.