Created attachment 1666142 [details] `journalctl --no-hostname -k > dmesg.txt 1. Please describe the problem: Hi, I have: a T480s. a Lenovo Thunderbolt docking station 3 3 Dell UH2419H screens, in daisy chain. Since the latest firmware updates and OS updates, the entire system is failing to properly display. The first screen usually complains about "no DP signal"- There are many errors in journalctl. 2. What is the Version-Release number of the kernel: 5.5.5-200.fc31.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : Yes it worked, but it's always not behaving well. I used to have as workaround simply to unplug the power suply of the docking. Lately that does not work. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes but it's random. It's very often though. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: No idea. 6. Are you running any modules that not shipped with directly Fedora's kernel?: I don't think so. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. See dmesg for: `journalctl --no-hostname -k > dmesg.txt See dmesg2 for `journalctl -b --no-hostname -k > dmesg.txt I also attached var log messages.
Created attachment 1666143 [details] `journalctl --no-hostname -k > dmesg2.txt
Created attachment 1666144 [details] journalctl beofre reboot
Created attachment 1666145 [details] journalctl error
I should have specified that when I do list "bolctl list", I see the docking connected (even when I get the NO DP signal on the first screen): boltctl list ● Lenovo ThinkPad Thunderbolt 3 Dock ├─ type: peripheral ├─ name: ThinkPad Thunderbolt 3 Dock ├─ vendor: Lenovo ├─ uuid: 000f3958-1ccb-0801-ffff-ffffffffffff ├─ status: authorized │ ├─ domain: cb010000-0082-8098-2022-ad1c5402eb22 │ └─ authflags: none ├─ authorized: Thu 27 Feb 2020 07:51:28 UTC ├─ connected: Thu 27 Feb 2020 07:51:28 UTC └─ stored: Thu 27 Feb 2020 07:32:18 UTC ├─ policy: iommu └─ key: no I tried various restarts of bolt service, etc...systemctl status bolt.service. The docking seems to misbehave badly too.
This is one of the errors I could see in journalctl -p 4: Feb 27 08:31:49 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: Host not accessible, reset failed. Feb 27 08:32:10 localhost.localdomain kernel: pcieport 0000:05:00.0: ASPM: current common clock configuration is broken, reconfiguring Feb 27 08:32:17 localhost.localdomain kernel: pcieport 0000:05:01.0: ASPM: current common clock configuration is broken, reconfiguring Feb 27 08:32:18 localhost.localdomain colord[2032]: failed to get session [pid 5527]: No data available Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain rtkit-daemon[1437]: Recovering from system lockup, not allowing further RT threads. Feb 27 08:32:19 localhost.localdomain colord[2032]: failed to get session [pid 5527]: No data available Feb 27 08:32:20 localhost.localdomain gnome-shell[5220]: Failed to use linear monitor configuration: No available CRTC for monitor 'DEL DELL U2419H' not found Feb 27 08:32:20 localhost.localdomain colord[2032]: failed to get session [pid 5527]: No data available Feb 27 08:32:20 localhost.localdomain gnome-shell[5220]: Failed to use linear monitor configuration: No available CRTC for monitor 'DEL DELL U2419H' not found Feb 27 08:32:38 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: xHCI host controller not responding, assume dead Feb 27 08:32:38 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: Host halt failed, -19 Feb 27 08:32:38 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: Host not accessible, reset failed. Feb 27 08:33:26 localhost.localdomain kernel: pcieport 0000:08:01.0: can't change power state from D3cold to D0 (config space inaccessible) Feb 27 08:33:26 localhost.localdomain kernel: pcieport 0000:08:03.0: can't change power state from D3cold to D0 (config space inaccessible) Feb 27 08:33:26 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: xHCI host controller not responding, assume dead Feb 27 08:33:26 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: Host halt failed, -19 Feb 27 08:33:26 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: Host not accessible, reset failed. Feb 27 08:33:26 localhost.localdomain kernel: pcieport 0000:08:01.0: can't change power state from D3cold to D0 (config space inaccessible) Feb 27 08:33:26 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: xHCI host controller not responding, assume dead Feb 27 08:33:26 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: Host halt failed, -19 Feb 27 08:33:26 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: Host not accessible, reset failed. Feb 27 08:33:31 localhost.localdomain kernel: thunderbolt 0000:06:00.0: no switch exists at 1.1, ignoring Feb 27 08:33:32 localhost.localdomain kernel: pcieport 0000:05:02.0: ASPM: current common clock configuration is broken, reconfiguring Feb 27 08:34:20 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: xHCI host controller not responding, assume dead Feb 27 08:34:20 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: HC died; cleaning up Feb 27 08:34:20 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: Host halt failed, -19 Feb 27 08:34:20 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: Host not accessible, reset failed. Feb 27 08:34:26 localhost.localdomain kernel: pcieport 0000:05:02.0: ASPM: current common clock configuration is broken, reconfiguring Feb 27 08:34:35 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: xHCI host controller not responding, assume dead Feb 27 08:34:35 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: HC died; cleaning up Feb 27 08:34:36 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: Host halt failed, -19 Feb 27 08:34:36 localhost.localdomain kernel: xhci_hcd 0000:3c:00.0: Host not accessible, reset failed. Feb 27 08:34:41 localhost.localdomain kernel: pcieport 0000:05:02.0: can't change power state from D3cold to D0 (config space inaccessible) Feb 27 08:34:41 localhost.localdomain kernel: pcieport 0000:05:00.0: can't change power state from D3cold to D0 (config space inaccessible)
[xxx@localhost ~]$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:16.3 Serial controller: Intel Corporation Sunrise Point-LP Active Management Technology - SOL (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point LPC Controller/eSPI Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-LM (rev 21) 04:00.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 05:00.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 05:01.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 05:02.0 PCI bridge: Intel Corporation JHL6240 Thunderbolt 3 Bridge (Low Power) [Alpine Ridge LP 2016] (rev 01) 06:00.0 System peripheral: Intel Corporation JHL6240 Thunderbolt 3 NHI (Low Power) [Alpine Ridge LP 2016] (rev 01) 07:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 08:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 08:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 08:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 08:03.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 08:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] (rev 02) 09:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) 0b:00.0 USB controller: Fresco Logic FL1100 USB 3.0 Host Controller (rev 10) 3d:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 3e:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [xxx@localhost ~]$ date Thu 27 Feb 09:52:51 CET 2020
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
Hi, It appears that with kernel 5.5.7-200.fc31.x86_64, I had less issues. I was only able to test for a few minutes.
Hi,The issue occured again: Mar 26 07:46:33 localhost.localdomain kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. Mar 26 07:46:33 localhost.localdomain kernel: TAA CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/tsx_async_abort.html for m> Mar 26 07:46:33 localhost.localdomain kernel: #5 #6 #7 Mar 26 07:46:33 localhost.localdomain kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' Mar 26 07:46:33 localhost.localdomain kernel: usb: port power management may be unreliable Mar 26 07:46:33 localhost.localdomain kernel: usb 1-2: device descriptor read/64, error -71 Mar 26 07:46:33 localhost.localdomain systemd-vconsole-setup[311]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented Mar 26 07:46:33 localhost.localdomain systemd-vconsole-setup[311]: Fonts will not be copied to remaining consoles Mar 26 07:46:33 localhost.localdomain kernel: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Mar 26 07:46:33 localhost.localdomain kernel: acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) Mar 26 07:46:34 localhost.localdomain systemd-vconsole-setup[519]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented Mar 26 07:46:34 localhost.localdomain systemd-vconsole-setup[519]: Fonts will not be copied to remaining consoles Mar 26 07:46:34 localhost.localdomain systemd-vconsole-setup[568]: KD_FONT_OP_GET failed while trying to get the font metadata: Function not implemented Mar 26 07:46:34 localhost.localdomain systemd-vconsole-setup[568]: Fonts will not be copied to remaining consoles Mar 26 07:47:01 localhost.localdomain systemd-vconsole-setup[1461]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument Mar 26 07:47:01 localhost.localdomain systemd-vconsole-setup[1461]: Fonts will not be copied to remaining consoles Mar 26 07:47:02 localhost.localdomain kernel: printk: systemd: 25 output lines suppressed due to ratelimiting Mar 26 07:47:02 localhost.localdomain systemd-vconsole-setup[1505]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument Mar 26 07:47:02 localhost.localdomain systemd-vconsole-setup[1505]: Fonts will not be copied to remaining consoles Mar 26 07:47:02 localhost.localdomain kernel: uvcvideo 1-8:1.0: Entity type for entity Realtek Extended Controls Unit was not initialized! Mar 26 07:47:02 localhost.localdomain kernel: uvcvideo 1-8:1.0: Entity type for entity Extension 4 was not initialized! Mar 26 07:47:02 localhost.localdomain kernel: uvcvideo 1-8:1.0: Entity type for entity Processing 2 was not initialized! Mar 26 07:47:02 localhost.localdomain kernel: uvcvideo 1-8:1.0: Entity type for entity Camera 1 was not initialized! Mar 26 07:47:02 localhost.localdomain systemd-udevd[1522]: event5: Process 'libinput-fuzz-to-zero /sys/devices/platform/i8042/serio1/input/input5/event5' failed with exit code 1. Mar 26 07:47:02 localhost.localdomain kernel: resource sanity check: requesting [mem 0xfed10000-0xfed15fff], which spans more than pnp 00:08 [mem 0xfed10000-0xfed13fff] Mar 26 07:47:02 localhost.localdomain kernel: caller snb_uncore_imc_init_box+0x6c/0xb0 [intel_uncore] mapping multiple BARs Mar 26 07:47:03 localhost.localdomain systemd-vconsole-setup[1606]: KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument Mar 26 07:47:03 localhost.localdomain systemd-vconsole-setup[1606]: Fonts will not be copied to remaining consoles Mar 26 07:47:03 localhost.localdomain kernel: thermal thermal_zone6: failed to read out thermal zone (-61) Mar 26 07:47:03 localhost.localdomain kernel: elan_i2c 10-0015: 10-0015 supply vcc not found, using dummy regulator Mar 26 07:47:03 localhost.localdomain avahi-daemon[1729]: System host name is set to 'localhost'. This is not a suitable mDNS host name, looking for alternatives. Mar 26 07:47:04 localhost.localdomain colord[2197]: failed to get session [pid 2095]: No data available Mar 26 07:47:04 localhost.localdomain colord[2197]: failed to get session [pid 2095]: No data available Mar 26 07:47:05 localhost.localdomain kernel: iwlwifi 0000:3d:00.0: FW already configured (0) - re-configuring Mar 26 07:47:05 localhost.localdomain kernel: iwlwifi 0000:3d:00.0: FW already configured (0) - re-configuring Mar 26 07:47:05 localhost.localdomain NetworkManager[2021]: <warn> [1585205225.5355] sup-iface: failed to cancel p2p connect: P2P cancel failed ar 26 07:47:05 localhost.localdomain systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. Mar 26 07:47:05 localhost.localdomain systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. Mar 26 07:47:06 localhost.localdomain kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.ht> Mar 26 07:47:07 localhost.localdomain dbus-broker-launch[4561]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Sources.service' is not named after the D-Bus name > Mar 26 07:47:07 localhost.localdomain dbus-broker-launch[4561]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Calendar.service' is not named after the D-Bus name> Mar 26 07:47:07 localhost.localdomain dbus-broker-launch[4561]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.UserPrompter.service' is not named after the D-Bus > Mar 26 07:47:07 localhost.localdomain dbus-broker-launch[4561]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.AddressBook.service' is not named after the D-Bus n> Mar 26 07:47:07 localhost.localdomain gnome-session-c[4608]: Error creating FIFO: File exists Mar 26 07:47:07 localhost.localdomain kernel: usb 3-1: 1:1: cannot get freq at ep 0x81 Mar 26 07:47:08 localhost.localdomain gnome-shell[4637]: Failed to use linear monitor configuration: No available CRTC for monitor 'DEL DELL U2419H' not found Mar 26 07:47:08 localhost.localdomain kernel: ucsi_acpi USBC000:00: con2: failed to register alternate modes Mar 26 07:47:09 localhost.localdomain kernel: typec_displayport port1-partner.0: failed to enter mode Mar 26 07:47:09 localhost.localdomain gnome-shell[4637]: Getting invalid resource scale property Mar 26 07:47:09 localhost.localdomain gnome-shell[4637]: ibus_bus_hello: assertion 'ibus_bus_is_connected (bus)' failed Mar 26 07:47:09 localhost.localdomain gnome-shell[4637]: Error while sending AddMatch() message: The connection is closed Mar 26 07:47:09 localhost.localdomain gnome-shell[4637]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed Mar 26 07:47:09 localhost.localdomain gnome-shell[4637]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed Mar 26 07:47:09 localhost.localdomain systemd[4452]: gnome-launched-spice-vdagent.desktop-4971.scope: Failed to add PIDs to scope's control group: No such process Mar 26 07:47:09 localhost.localdomain systemd[4452]: gnome-launched-spice-vdagent.desktop-4971.scope: Failed with result 'resources'. Mar 26 07:47:09 localhost.localdomain systemd[4452]: Failed to start Application launched by gnome-session-binary. Mar 26 07:47:11 localhost.localdomain dbus-broker-launch[1761]: Activation request for 'org.freedesktop.resolve1' failed: The systemd unit 'dbus-org.freedesktop.resolve1.service' could no> Mar 26 07:47:11 localhost.localdomain systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. Mar 26 07:47:12 localhost.localdomain gsd-media-keys[4968]: Failed to grab accelerator for keybinding settings:playback-random Mar 26 07:47:12 localhost.localdomain gsd-media-keys[4968]: Failed to grab accelerator for keybinding settings:playback-repeat Mar 26 07:47:12 localhost.localdomain gsd-media-keys[4968]: Failed to grab accelerator for keybinding settings:rfkill Mar 26 07:47:12 localhost.localdomain gsd-media-keys[4968]: Failed to grab accelerator for keybinding settings:hibernate Mar 26 07:47:12 localhost.localdomain gsd-power[4970]: Unable to inhibit suspend: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for i> Mar 26 07:47:55 localhost.localdomain kernel: pcieport 0000:07:00.0: can't change power state from unknown to D0 (config space inaccessible) Mar 26 07:47:55 localhost.localdomain kernel: pcieport 0000:08:00.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:55 localhost.localdomain kernel: pcieport 0000:08:01.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:55 localhost.localdomain kernel: pcieport 0000:08:02.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:55 localhost.localdomain kernel: pcieport 0000:08:03.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:55 localhost.localdomain kernel: pcieport 0000:08:04.0: can't change power state from unknown to D0 (config space inaccessible) Mar 26 07:47:55 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: Controller not ready at resume -19 Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: PCI post-resume error -19! Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: HC died; cleaning up Mar 26 07:47:56 localhost.localdomain kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x80 returns -19 Mar 26 07:47:56 localhost.localdomain kernel: PM: Device 0000:09:00.0 failed to resume async: error -19 Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: can't change power state from D3hot to D0 (config space inaccessible) Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: Controller not ready at resume -19 Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: PCI post-resume error -19! Mar 26 07:47:56 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: HC died; cleaning up Mar 26 07:47:56 localhost.localdomain kernel: PM: dpm_run_callback(): pci_pm_resume+0x0/0x80 returns -19 Mar 26 07:47:56 localhost.localdomain kernel: PM: Device 0000:0b:00.0 failed to resume async: error -19 Mar 26 07:47:56 localhost.localdomain kernel: usb 2-3: Disable of device-initiated U1 failed. Mar 26 07:47:56 localhost.localdomain kernel: usb 2-3: Disable of device-initiated U2 failed. Mar 26 07:47:56 localhost.localdomain kernel: iwlwifi 0000:3d:00.0: FW already configured (0) - re-configuring Mar 26 07:47:56 localhost.localdomain kernel: done. Mar 26 07:47:55 localhost.localdomain NetworkManager[2021]: <warn> [1585205275.9687] sup-iface[0x56190d336120,wlp61s0]: connection disconnected (reason -3) Mar 26 07:47:55 localhost.localdomain wpa_supplicant[3351]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0 Mar 26 07:47:56 localhost.localdomain dnsmasq[3695]: no servers found in /etc/resolv.conf, will retry Mar 26 07:47:56 localhost.localdomain chronyd[1802]: Forward time jump detected! Mar 26 07:47:56 localhost.localdomain colord[2197]: failed to get session [pid 4965]: No data available Mar 26 07:47:56 localhost.localdomain kernel: iwlwifi 0000:3d:00.0: FW already configured (0) - re-configuring Mar 26 07:47:57 localhost.localdomain kernel: iwlwifi 0000:3d:00.0: FW already configured (0) - re-configuring Mar 26 07:48:02 localhost.localdomain colord[2197]: failed to get session [pid 4965]: No data available Mar 26 07:48:02 localhost.localdomain colord[2197]: failed to get session [pid 4965]: No data available Mar 26 07:48:02 localhost.localdomain systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. Mar 26 07:48:04 localhost.localdomain colord[2197]: failed to get session [pid 4965]: No data available Mar 26 07:48:41 localhost.localdomain gdm-password][5325]: gkr-pam: unable to locate daemon control file Mar 26 07:48:52 localhost.localdomain gnome-shell[4637]: Failed to use linear monitor configuration: No available CRTC for monitor 'AUO 0x243d' not found Mar 26 07:48:56 localhost.localdomain systemd-udevd[1516]: usb3: Worker [5256] processing SEQNUM=4491 is taking a long time Mar 26 07:49:10 localhost.localdomain gdm-password][5342]: gkr-pam: unable to locate daemon control file Mar 26 07:49:10 localhost.localdomain dbus-broker-launch[5403]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Sources.service' is not named after the D-Bus name > Mar 26 07:49:10 localhost.localdomain dbus-broker-launch[5403]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.Calendar.service' is not named after the D-Bus name> Mar 26 07:49:10 localhost.localdomain dbus-broker-launch[5403]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.UserPrompter.service' is not named after the D-Bus > Mar 26 07:49:10 localhost.localdomain dbus-broker-launch[5403]: Service file '/usr/share/dbus-1/services/org.gnome.evolution.dataserver.AddressBook.service' is not named after the D-Bus n> Mar 26 07:49:10 localhost.localdomain gnome-session-c[5458]: Error creating FIFO: File exists Mar 26 07:49:10 localhost.localdomain gnome-session-binary[5460]: GnomeDesktop-WARNING: Could not create transient scope for PID 5481: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessId> Mar 26 07:49:10 localhost.localdomain gnome-session-binary[5460]: GnomeDesktop-WARNING: Could not create transient scope for PID 5484: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessId> Mar 26 07:49:10 localhost.localdomain systemd[5368]: gnome-launched-gsettings-data-convert.desktop-5483.scope: Failed to add PIDs to scope's control group: No such process Mar 26 07:49:10 localhost.localdomain systemd[5368]: gnome-launched-gsettings-data-convert.desktop-5483.scope: Failed with result 'resources'. Mar 26 07:49:10 localhost.localdomain systemd[5368]: Failed to start Application launched by gnome-session-binary. Mar 26 07:49:11 localhost.localdomain gnome-shell[5480]: Failed to use linear monitor configuration: No available CRTC for monitor 'DEL DELL U2419H' not found Mar 26 07:49:11 localhost.localdomain gnome-shell[4637]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied Mar 26 07:49:12 localhost.localdomain goa-identity-se[5697]: GoaKerberosIdentityManager: Using polling for change notification for credential cache type 'KCM' Mar 26 07:49:12 localhost.localdomain goa-daemon[5669]: secret_password_lookup_sync() returned NULL Mar 26 07:49:12 localhost.localdomain gnome-shell[5480]: ibus_bus_hello: assertion 'ibus_bus_is_connected (bus)' failed Mar 26 07:49:12 localhost.localdomain gnome-shell[5480]: Error while sending AddMatch() message: The connection is closed Mar 26 07:49:12 localhost.localdomain gnome-shell[5480]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed Mar 26 07:49:12 localhost.localdomain gnome-shell[5480]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed Mar 26 07:49:12 localhost.localdomain vmware-user.desktop[5790]: vmware-user: could not open /proc/fs/vmblock/dev Mar 26 07:49:12 localhost.localdomain gnome-session-binary[5460]: GnomeDesktop-WARNING: Could not create transient scope for PID 5785: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessId> Mar 26 07:49:12 localhost.localdomain gnome-session-binary[5460]: GnomeDesktop-WARNING: Could not create transient scope for PID 5790: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessId> Mar 26 07:49:12 localhost.localdomain gnome-session-binary[5460]: GnomeDesktop-WARNING: Could not create transient scope for PID 5824: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessId> Mar 26 07:49:12 localhost.localdomain gnome-session-binary[5460]: GnomeDesktop-WARNING: Could not create transient scope for PID 5862: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessId> Mar 26 07:49:12 localhost.localdomain systemd[5368]: gnome-launched-tracker-store.desktop-5840.scope: Failed to add PIDs to scope's control group: No such process Mar 26 07:49:12 localhost.localdomain systemd[5368]: gnome-launched-tracker-store.desktop-5840.scope: Failed with result 'resources'. Mar 26 07:49:12 localhost.localdomain systemd[5368]: Failed to start Application launched by gnome-session-binary. Mar 26 07:49:13 localhost.localdomain gnome-shell[5480]: STACK_OP_ADD: window 0x800001 already in stack Mar 26 07:49:13 localhost.localdomain gnome-shell[5480]: STACK_OP_ADD: window 0x800001 already in stack Mar 26 07:49:13 localhost.localdomain gnome-shell[4637]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied Mar 26 07:49:13 localhost.localdomain goa-daemon[5669]: secret_password_lookup_sync() returned NULL Mar 26 07:49:13 localhost.localdomain SpiderOakGroups.desktop[5847]: "sni-qt/5847" WARN 07:49:13.569 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE Mar 26 07:49:13 localhost.localdomain SpiderOakGroups.desktop[5847]: No systemtrayicon available Mar 26 07:49:14 localhost.localdomain gsd-media-keys[5786]: Failed to grab accelerator for keybinding settings:playback-random Mar 26 07:49:14 localhost.localdomain gsd-media-keys[5786]: Failed to grab accelerator for keybinding settings:rfkill Mar 26 07:49:14 localhost.localdomain gsd-media-keys[5786]: Failed to grab accelerator for keybinding settings:hibernate Mar 26 07:49:14 localhost.localdomain gsd-media-keys[5786]: Failed to grab accelerator for keybinding settings:playback-repeat Mar 26 07:49:14 localhost.localdomain colord[2197]: failed to get session [pid 5779]: No data available Mar 26 07:49:14 localhost.localdomain colord[2197]: failed to get session [pid 5779]: No data available Mar 26 07:49:14 localhost.localdomain colord[2197]: failed to get session [pid 5779]: No data available Mar 26 07:49:14 localhost.localdomain libcanberra-login-sound.desktop[5796]: Failed to play sound: File or data not found Mar 26 07:49:14 localhost.localdomain colord[2197]: failed to get session [pid 5779]: No data available Mar 26 07:49:14 localhost.localdomain gnome-shell[4637]: Failed to CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied Mar 26 07:49:15 localhost.localdomain tpm2-abrmd[6233]: tcti_conf before: "device:/dev/tpm0" Mar 26 07:49:15 localhost.localdomain tpm2-abrmd[6233]: tcti_conf after: "device:/dev/tpm0" Mar 26 07:49:15 localhost.localdomain gsd-print-notif[4973]: Source ID 5 was not found when attempting to remove it Mar 26 07:49:15 localhost.localdomain gsd-color[5779]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2419H_> Mar 26 07:49:15 localhost.localdomain gsd-color[5779]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2419H_> Mar 26 07:49:15 localhost.localdomain gsd-color[5779]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2419H_> Mar 26 07:49:15 localhost.localdomain gsd-color[5779]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_AU_Optronics_gdm_42 Mar 26 07:49:15 localhost.localdomain gnome-shell[4637]: Connection to xwayland lost Mar 26 07:49:15 localhost.localdomain gnome-session-binary[4611]: WARNING: Could not get session class: No such device or address Mar 26 07:49:15 localhost.localdomain systemd[4452]: xdg-permission-store.service: Failed with result 'exit-code'. Mar 26 07:49:15 localhost.localdomain dbus-broker-launch[6274]: Service file '/usr/share//dbus-1/services/org.gnome.evolution.dataserver.Sources.service' is not named after the D-Bus name> Mar 26 07:49:15 localhost.localdomain dbus-broker-launch[6274]: Service file '/usr/share//dbus-1/services/org.gnome.evolution.dataserver.Calendar.service' is not named after the D-Bus nam> Mar 26 07:49:15 localhost.localdomain dbus-broker-launch[6274]: Service file '/usr/share//dbus-1/services/org.gnome.evolution.dataserver.UserPrompter.service' is not named after the D-Bus> Mar 26 07:49:15 localhost.localdomain dbus-broker-launch[6274]: Service file '/usr/share//dbus-1/services/org.gnome.evolution.dataserver.AddressBook.service' is not named after the D-Bus > Mar 26 07:49:15 localhost.localdomain spideroak_inotify[6162]: inotify_add_watch /home/user/Documents/SBBSept2019/CaseWithSoftResetUster/ust-ag01-i54x-003/sosreport-ust-ag01-i54x-003-2> Mar 26 07:49:21 localhost.localdomain spideroak_inotify[6290]: inotify_add_watch /home/user/Documents/SBBSept2019/zg-dg02-i54x-02/sosreport-zg-dg02-i54x-02-2019-09-30-ccjdbib/sys/devic> Mar 26 07:49:32 localhost.localdomain spideroak_inotify[6307]: inotify_add_watch /home/user/Documents/SBBSept2019/zg-dg02-i54x-02/sosreport-zg-dg02-i54x-02-2019-09-30-ccjdbib/proc/irq/> Mar 26 07:49:40 localhost.localdomain gnome-software[5842]: not GsPlugin error g-io-error-quark:24: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached Mar 26 07:49:40 localhost.localdomain gnome-software[5842]: not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached Mar 26 07:49:42 localhost.localdomain gnome-software[5842]: Only 5 apps for recent list, hiding Mar 26 07:49:47 localhost.localdomain spideroak_inotify[6355]: inotify_add_watch /home/user/Documents/SBBSept2019/zg-dg02-i54x-02/sosreport-zg-dg02-i54x-02-2019-09-30-ccjdbib/proc/irq/> Mar 26 07:50:08 localhost.localdomain gnome-software[5842]: updates-shell: failed to get updates: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached Mar 26 07:50:11 localhost.localdomain colord[2197]: failed to get session [pid 5779]: No data available Mar 26 07:50:12 localhost.localdomain colord[2197]: failed to get session [pid 5779]: No data available Mar 26 07:50:12 localhost.localdomain colord[2197]: failed to get session [pid 5779]: No data available Mar 26 07:50:40 localhost.localdomain gnome-software[5842]: not GsPlugin error g-io-error-quark:24: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached Mar 26 07:50:40 localhost.localdomain gnome-software[5842]: not handling error failed for action refresh: Error calling StartServiceByName for org.freedesktop.fwupd: Timeout was reached Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble' Mar 26 07:50:44 localhost.localdomain gnome-shell[5480]: value "nan" of type 'gdouble' is invalid or out of range for property 'vignette-sharpness' of type 'gdouble'
By the way I am now on 5.5.10-200.fc31.x86_64. I think it has something to do with the docking, I already asked Lenovo support and they are sending me a replacement so I can test if that's the root cause. When I fully power it off, remove it's power, unplug ther usb and reconnect it, I am sometimes able to recover the screens (which means to have the 3 screens display the image). Remember they are daisy chained also. I have noticed that if anything is usb connected to one screen and connected to the docking with the usb, it's worse. Sometimes when I start the laptop, it gets completely confused and display 2 screens over 3 (the last one claiming there is no DP signal, eventhough the screen is the first on the daisy chain). When that happens it blinks black every 30-1minutes as in it's trying to reload the screens or redetect. Let me explain better: Screen 1 ----> DaiyChained ----> Screen 2 ---> Daisy Chained ---> Screen 3. I had screen 2 and 3 with proper image of my Fedora desktop, screen 1 was claiming no DP signal. It seems the T480s/docking are failing with that config. The screens are 3 U2419H ultrasharp. I noticed it gets worse when anything is USB connected to one of the screen. I had the laptop/mouse in screen 1 (and then the USB from screen 1 to the docking). I also had a speaker in Screen 2 usb (it's only used when everything is power off, expect screen 2, as HDMI, with a PS4 Pro :) ). The simple presence of the usb in screen 2 seems to also impact the detection as when I remove any usb screen it seems I get it to work a bit faster (or with less retries). Thanks,
Hi, I have the strong feeling that the issue is related to the docking. Something in it saves a state, probably with USB devices (like mouse, screen) and it's trying to somehow recover that. FYI, I just had a replacement docking from Lenovo it happens again. But the first time, it went smoothly. It's only the second boot, today, when I reconnected usb devices, and booted the laptop, that it misbehaves. The workaround is to power off that docking (remove power cable), remove known devices (in Fedora Gui, Device/Thunderbolt/ Forget Device), etc... I have tried to recover opening/closing the laptop lids. It failed. Only the middle screen shown output. Then I tried powering off/on the docking removing the power cable. It failed. It was not able to redisplay the 3 screens. Then I removed the USB cable from the docking to the screen 1 (it has 2 usb devices connected to the screen 1, a mouse and keyboard). Then closed, open the laptop lid, and it works. So as I said I suspect it is really something happening when there's a USB device connected to the screen and then indirectly to the docking. Cheers, I attached some latest dmesg files.
Created attachment 1674654 [details] dmesg kernel
Created attachment 1674655 [details] full dmesg after boot
The docking is a Lenovo Thunderbolt 3 Dock Type 40AC SN ZBK0KWAQ 19/03 DBB9003L1
Created attachment 1674763 [details] journalctl errors since 9am until now 30th march 2020 I added the journalctl with interesting errors like: : Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with> Jan 05 17:28:32 localhost.localdomain gnome-shell[3760]: The offending signal was destroy on Gjs_IconGrid 0x56487d20d4d0. Mar 30 17:50:08 localhost.localdomain gsd-color[4741]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Dell_Inc__DELL_U2419H_6QCCKS2_jtougne_1000 Mar 30 17:50:09 localhost.localdomain gsd-color[4741]: could not find device: property match 'XRANDR_name'='DP-5' does not exist I don't have a "DP-5" device...
Same problem on Fedora 32: Apr 29 08:11:07 localhost.localdomain kernel: pcieport 0000:08:03.0: can't change power state from D3cold to D0 (config space inaccessible) Apr 29 08:11:07 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: xHCI host controller not responding, assume dead Apr 29 08:11:07 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: Host halt failed, -19 Apr 29 08:11:07 localhost.localdomain kernel: xhci_hcd 0000:0b:00.0: Host not accessible, reset failed. Apr 29 08:11:07 localhost.localdomain kernel: pcieport 0000:08:01.0: can't change power state from D3cold to D0 (config space inaccessible) Apr 29 08:11:07 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: xHCI host controller not responding, assume dead Apr 29 08:11:07 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: Host halt failed, -19 Apr 29 08:11:07 localhost.localdomain kernel: xhci_hcd 0000:09:00.0: Host not accessible, reset failed. Apr 29 08:11:07 localhost.localdomain gsd-media-keys[5196]: Unable to get default source kernel: 5.6.6-300.fc32.x86_64
Hi, I run Arch (5.6.15), not Fedora, and don't have this particular DP-MST setup but a single DP-4k screen BUT I have the exact same error messages with my T480 on an ThinkPad Thunderbolt 3 Dock Gen2 (both with the current FW). Furthermore I noticed that pulling the power plug from my screen for a few seconds reliably solves the issue. :S Hence I also strongly suspect the docking station. I thought this might be helpful for whoever wherever haunts this bug.
I think I'm having the same problem, with a different laptop model (Lenovo P1 Gen 2) but the same Dock (Thunderbolt 3 Gen 2 Dock) on a fully up to date Fedora 32: ``` $ boltctl list ● Lenovo ThinkPad Thunderbolt 3 Dock ├─ type: peripheral ├─ name: ThinkPad Thunderbolt 3 Dock ├─ vendor: Lenovo ├─ uuid: 00c55278-499f-0801-ffff-ffffffffffff ├─ status: authorized │ ├─ domain: c3030000-0062-6c0e-03f7-983932d19100 │ └─ authflags: boot ├─ authorized: Mo 22 Jun 2020 07:08:22 UTC ├─ connected: Mo 22 Jun 2020 07:08:21 UTC └─ stored: Fr 19 Jun 2020 14:59:47 UTC ├─ policy: auto └─ key: no $ uname -a Linux guarana 5.6.19-300.fc32.x86_64 #1 SMP Wed Jun 17 16:10:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` It wasn't clear from the original report, but I wanted to share that all the devices seems to be restarted, including network devices, meaning that all interfaces are restarted as well (including VPN). I can somewhat consistently reproduce this bug by hitting the super key and entering a search term in Gnome shell ("firefox" to open Firefox, for instance). Once I disconnected all USB devices from the dock, it _seems_ to be better. This bug is really annoying :)
(In reply to Juraci Paixão Kröhling from comment #18) > Once I disconnected all USB devices from the dock, it _seems_ to be better. This proved to be false: it happens just as often as before.
Apparently, this might be a hardware issue after all. I confirmed that the problem with my setup was indeed due to the dock, as I was able to work without interruptions when the laptop wasn't connected to it. A valid workaround seems to be to plug the power source to both the laptop and the dock.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.