Red Hat Bugzilla – Bug 1477182
Lenovo P50: DP does not connect unless the connection is present at boot time
Last modified: 2018-05-22 16:08:48 EDT
Description of problem:
I have a Lenovo P50 with an external Monitor connected via Display Port. The system boots and presents the monitor successfully. Once the system has booted, I disconnect and reconnect the DP cable (undocking and redocking produces the same result). The monitor is no longer recognized. On rare occasions (~1 out of 25 tries), it works. Rebooting with the monitor connected solves the problem. The chances for a succesful connection seems to be better for the first try after a reboot.
Everything works as expected, if the connection is made through the HDMI port of the laptop itself. The HDMI port on the dock uses DP-MST as connection and does not work. I assume the problem does only concern DP.
Version-Release number of selected component (if applicable):
Linux gerty 4.11.11-300.fc26.x86_64 #1 SMP Mon Jul 17 16:32:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
dnf info xorg-x11-drv-nouveau:
Name : xorg-x11-drv-nouveau
Epoch : 1
Version : 1.0.15
Release : 1.fc26
Arch : x86_64
Size : 219 k
Source : xorg-x11-drv-nouveau-1.0.15-1.fc26.src.rpm
Repo : @System
From repo : fedora
Summary : Xorg X11 nouveau video driver for NVIDIA graphics chipsets
URL : http://www.x.org
License : MIT
Description : X.Org X11 nouveau video driver.
Steps to Reproduce:
1. Boot up P50 with monitor connected through DP
2. Disconnect DP cable
3. Reconnect DP cable
Monitor is no longer recognized (not connected in xrandr/Gnome Display Settings)
Monitor is recognized.
dmesg output for disconnect:
[ 59.718284] nouveau 0000:01:00.0: DRM: suspending console...
[ 59.718289] nouveau 0000:01:00.0: DRM: suspending display...
[ 59.718323] nouveau 0000:01:00.0: DRM: evicting buffers...
[ 59.800927] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[ 59.800949] nouveau 0000:01:00.0: DRM: suspending fence...
[ 59.803672] nouveau 0000:01:00.0: DRM: suspending object tree...
dmesg output for successful connect:
[ 78.254497] nouveau 0000:01:00.0: DRM: resuming object tree...
[ 78.399369] nouveau 0000:01:00.0: priv: HUB0: 614900 00800000 (1d408200)
[ 78.569793] nouveau 0000:01:00.0: DRM: resuming fence...
[ 78.569817] nouveau 0000:01:00.0: DRM: resuming display...
[ 78.569914] nouveau 0000:01:00.0: DRM: resuming console...
[ 87.212999] nouveau 0000:01:00.0: disp: 0x64a8: INIT_GENERIC_CONDITON: unknown 0x07
dmesg output for unseccesful connect:
[ 378.239501] nouveau 0000:01:00.0: DRM: resuming object tree...
[ 378.384399] nouveau 0000:01:00.0: priv: HUB0: 614900 00800000 (1e408200)
[ 378.554878] nouveau 0000:01:00.0: DRM: resuming fence...
[ 378.554903] nouveau 0000:01:00.0: DRM: resuming display...
[ 378.556371] nouveau 0000:01:00.0: DRM: resuming console...
[ 383.814940] nouveau 0000:01:00.0: DRM: suspending console...
[ 383.814944] nouveau 0000:01:00.0: DRM: suspending display...
[ 383.815423] nouveau 0000:01:00.0: DRM: evicting buffers...
[ 383.815426] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[ 383.815456] nouveau 0000:01:00.0: DRM: suspending fence...
[ 383.818837] nouveau 0000:01:00.0: DRM: suspending object tree...
I have exactly the same problem on the same hardware.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1527669 , P50 not booting when docked.
I have seen the docking station monitor recognized *sometimes* after docking while the P50 was awake. I have yet to identify a specific pattern of when it might or might not happen.
Sometimes the internal laptop display is not recognized. I work around that by suspending and waking the system, connecting another display to the mini DVI port, or rebooting if that fails.
FWIW, my P50 connects external DPs (both on-the-box and on-the-dock)
with a *much* higher success rate; haven't measured but I'd say above
80%. My setup:
* the discrete card only (set in BIOS/UEFI)
* the notebook is always awake
* kernel-4.16.0-*.fc29.x86_64 (from fedora-rawhide-kernel-nodebug,
in hope to get rid of bz1527669 and bz1511786 but no luck yet)
If a connection fails, re-attaching usually helps. IIRC, I haven't
needed a reboot so far.
Same problem as reported in comment 0 here. Though, since I also run into bz1527669 connection at boot time is somewhat problematic. I have:
All of these kernels seem to have the problem:
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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'
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 26 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.
Changing to F27 since I've got this exact problem there too.
I have exactly same problem with Lenovo P50 (Optimus/Prime issue? Integrated Intel graphics card, discrete NVidia) on Fedora 28 (using XFce):
I have upgraded to to F28 from F27 some time ago and in F27 it worked for me quite quite reliably for about 2 months ago.