Bug 1322421

Summary: system appears to hang after removing Lenovo T440s laptop from docking station
Product: [Fedora] Fedora Reporter: Micah Abbott <miabbott>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: ajax, ewoud+redhat, fmuellner, gansalmon, gravasio, iiro.hietala, itamar, jonathan, kernel-maint, labbott, leho, madhu.chinakonda, mchehab, otaylor, sander, valent.turkovic, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 19:43:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Micah Abbott 2016-03-30 13:21:38 UTC 
Description of problem:

After undocking my laptop from my docking station, occasionally gnome-shell will appear to hang.


Version-Release number of selected component (if applicable):

gnome-shell-3.18.4-1.fc23.x86_64
kernel-4.4.6-300.fc23.x86_64

How reproducible:

Intermittent


Steps to Reproduce:

1.  Undock laptop from docking station with active user session (logged in to GNOME, etc)


Actual results:

System appears to hang, no input via keyboard or mouse seems to take effect.


Expected results:

GNOME menubar at top of session should be redrawn on laptop display, system should accept input.


Additional info:

My laptop is a Lenovo Thinkpad T440s docked to an Ultradock with two monitors connected via DP.

When I un-dock for the day, I typically only have GNOME Terminal running in my session, usually on one of the connected monitors.  Sometimes everything just works normally when I un-dock; the terminal is re-drawn to the laptop display and I can continue to use it.  However, often, this does not happen and my only recourse is to hard shutdown the laptop via the power button.


There is a warning message in the journal from gnome-shell, but it doesn't appear to be a smoking gun.  See below (with a bit of context)


Mar 29 17:56:53 mastershake audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 29 17:57:19 mastershake gnome-shell.desktop[2790]: Window manager warning: last_focus_time (46163015) is greater than comparison timestamp (46163004).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Mar 29 17:57:24 mastershake audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-machined comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Comment 1 Micah Abbott 2016-03-31 14:21:29 UTC 
This happened again last night when I un-docked.  Instead of hard powering off, I closed the lid on the laptop and just let it do its thing.

When I checked the journal this morning, I found a number of more interesting messages:


Mar 30 17:20:23 mastershake kernel: [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate vcpi
Mar 30 17:20:23 mastershake kernel: [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A
Mar 30 17:20:23 mastershake kernel: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Mar 30 17:20:23 mastershake kernel: ------------[ cut here ]------------
Mar 30 17:20:23 mastershake kernel: WARNING: CPU: 2 PID: 2544 at drivers/gpu/drm/i915/intel_display.c:12742 intel_atomic_commit+0xf1a/0x1420 [i915]()
Mar 30 17:20:23 mastershake kernel: encoder detached but still enabled on pipe A.
Mar 30 17:20:23 mastershake kernel: Modules linked in: vhost_net vhost macvtap macvlan fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_addrtype br_netfilter nf_conntrack_netbios_ns nf_conntrack_bro
Mar 30 17:20:23 mastershake kernel:  cfg80211 videobuf2_memops videobuf2_v4l2 joydev videobuf2_core v4l2_common btusb btrtl rtsx_pci_ms videodev btbcm btintel mei_me i2c_i801 memstick snd_hda_codec_realtek lpc_i
Mar 30 17:20:23 mastershake kernel: CPU: 2 PID: 2544 Comm: Xorg Not tainted 4.4.6-300.fc23.x86_64 #1
Mar 30 17:20:23 mastershake kernel: Hardware name: LENOVO 20ARS0LE00/20ARS0LE00, BIOS GJET75WW (2.25 ) 03/28/2014
Mar 30 17:20:23 mastershake kernel:  0000000000000286 00000000e38fb233 ffff8802e909fb20 ffffffff813b542e
Mar 30 17:20:23 mastershake kernel:  ffff8802e909fb68 ffffffffa0242de8 ffff8802e909fb58 ffffffff810a40f2
Mar 30 17:20:23 mastershake kernel:  ffff88030cd00b18 ffff88030f857000 ffff88030cd00b30 ffff88030cd00800
Mar 30 17:20:23 mastershake kernel: Call Trace:
Mar 30 17:20:23 mastershake kernel:  [<ffffffff813b542e>] dump_stack+0x63/0x85
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810a40f2>] warn_slowpath_common+0x82/0xc0
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810a418c>] warn_slowpath_fmt+0x5c/0x80
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa01e017a>] intel_atomic_commit+0xf1a/0x1420 [i915]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa006b1be>] ? drm_atomic_check_only+0x18e/0x590 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa006b5f7>] drm_atomic_commit+0x37/0x60 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa00c34c6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa005ab62>] drm_mode_set_config_internal+0x62/0x100 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa005eee2>] drm_mode_setcrtc+0x3d2/0x4f0 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa0050602>] drm_ioctl+0x152/0x540 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa005eb10>] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffff8133fc9c>] ? selinux_file_ioctl+0x10c/0x1c0
Mar 30 17:20:23 mastershake kernel:  [<ffffffff81241248>] do_vfs_ioctl+0x298/0x480
Mar 30 17:20:23 mastershake kernel:  [<ffffffff81337553>] ? security_file_ioctl+0x43/0x60
Mar 30 17:20:23 mastershake kernel:  [<ffffffff812414a9>] SyS_ioctl+0x79/0x90
Mar 30 17:20:23 mastershake kernel:  [<ffffffff817a04ee>] entry_SYSCALL_64_fastpath+0x12/0x71
Mar 30 17:20:23 mastershake kernel: ---[ end trace 50d4175ce2d1cd42 ]---
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (II) config/udev: removing device Logitech USB Optical Mouse
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (**) Option "fd" "20"
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (II) UnloadModule: "libinput"
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (II) systemd-logind: releasing fd for 13:72
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (EE) systemd-logind: failed to release device: Device not taken
Mar 30 17:20:23 mastershake kernel: thinkpad_acpi: undocked from hotplug port replicator
Mar 30 17:20:23 mastershake kernel: usb 3-3: USB disconnect, device number 2
Mar 30 17:20:23 mastershake kernel: ------------[ cut here ]------------
Mar 30 17:20:23 mastershake kernel: WARNING: CPU: 1 PID: 6832 at drivers/gpu/drm/i915/intel_display.c:12734 intel_atomic_commit+0xc38/0x1420 [i915]()
Mar 30 17:20:23 mastershake kernel: encoder's enabled state mismatch (expected 1, found 0)
Mar 30 17:20:23 mastershake kernel: Modules linked in: vhost_net vhost macvtap macvlan fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_addrtype br_netfilter nf_conntrack_netbios_ns nf_conntrack_bro
Mar 30 17:20:23 mastershake kernel:  cfg80211 videobuf2_memops videobuf2_v4l2 joydev videobuf2_core v4l2_common btusb btrtl rtsx_pci_ms videodev btbcm btintel mei_me i2c_i801 memstick snd_hda_codec_realtek lpc_i
Mar 30 17:20:23 mastershake kernel: CPU: 1 PID: 6832 Comm: kworker/1:5 Tainted: G        W       4.4.6-300.fc23.x86_64 #1
Mar 30 17:20:23 mastershake kernel: Hardware name: LENOVO 20ARS0LE00/20ARS0LE00, BIOS GJET75WW (2.25 ) 03/28/2014
Mar 30 17:20:23 mastershake kernel: Workqueue: events drm_dp_destroy_connector_work [drm_kms_helper]
Mar 30 17:20:23 mastershake kernel:  0000000000000286 0000000059705135 ffff880185a1bbb0 ffffffff813b542e
Mar 30 17:20:23 mastershake kernel:  ffff880185a1bbf8 ffffffffa0242de8 ffff880185a1bbe8 ffffffff810a40f2
Mar 30 17:20:23 mastershake kernel:  ffff88030cd00b18 ffff88030ccbe900 ffff88030cd00b30 ffff88030cd00800
Mar 30 17:20:23 mastershake kernel: Call Trace:
Mar 30 17:20:23 mastershake kernel:  [<ffffffff813b542e>] dump_stack+0x63/0x85
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810a40f2>] warn_slowpath_common+0x82/0xc0
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810a418c>] warn_slowpath_fmt+0x5c/0x80
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa01dfe98>] intel_atomic_commit+0xc38/0x1420 [i915]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa006b1be>] ? drm_atomic_check_only+0x18e/0x590 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa006b5f7>] drm_atomic_commit+0x37/0x60 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa00c34c6>] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa0069f12>] ? drm_modeset_lock_all+0xa2/0xe0 [drm]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa020128c>] intel_dp_destroy_mst_connector+0x5c/0x110 [i915]
Mar 30 17:20:23 mastershake kernel:  [<ffffffffa00bf36c>] drm_dp_destroy_connector_work+0x8c/0x130 [drm_kms_helper]
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810bc596>] process_one_work+0x156/0x430
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810bc8be>] worker_thread+0x4e/0x450
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810bc870>] ? process_one_work+0x430/0x430
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810c2648>] kthread+0xd8/0xf0
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810c2570>] ? kthread_worker_fn+0x160/0x160
Mar 30 17:20:23 mastershake kernel:  [<ffffffff817a084f>] ret_from_fork+0x3f/0x70
Mar 30 17:20:23 mastershake kernel:  [<ffffffff810c2570>] ? kthread_worker_fn+0x160/0x160
Mar 30 17:20:23 mastershake kernel: ---[ end trace 50d4175ce2d1cd43 ]---
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (EE) intel(0): page flipping failed, on CRTC:25 (pipe=1), disabling synchronous page flips
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (EE) intel(0): failed to set mode: No such file or directory [2]
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (II) intel(0): Disabled output DP2-1
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (II) intel(0): Disabled output DP2-2
Mar 30 17:20:23 mastershake /usr/libexec/gdm-x-session[2537]: (II) intel(0): Disabled output DP2-3



Hunting around for the first error message ("failed to allocate vcpi") led me to this patch, which looks relevant:

https://lkml.org/lkml/2016/3/16/738

...which leads me to believe this is actually a kernel issue and not gnome-shell.


I've updated the summary and changed the component as such.
Comment 2 Giuseppe Ravasio 2016-05-05 20:30:44 UTC 
Same problem here!
Comment 3 Valent Turkovic 2016-05-24 17:48:12 UTC 
Is there a workaround for this issue?
Comment 4 Ewoud Kohl van Wijngaarden 2016-05-26 12:38:55 UTC 
My issue is similar, but not quite the same. From the journal:

mei 20 12:44:48 lampje kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (EE) intel(0): page flipping failed, on CRTC:21 (pipe=0), disabling synchronous page flips
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) intel(0): switch to mode 2560x1440 on DP2-2 using pipe 0, position (0, 0), rotation normal, reflection none
mei 20 12:44:48 lampje kernel: usb 3-3: USB disconnect, device number 6
mei 20 12:44:48 lampje kernel: thinkpad_acpi: undocked from hotplug port replicator
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (EE) intel(0): failed to set mode: No such file or directory [2]
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) intel(0): Disabled output DP2-1
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) intel(0): Disabled output DP2-2
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) intel(0): Disabled output DP2-3
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) intel(0): switch to mode 1920x1080 on eDP1 using pipe 1, position (2560, 360), rotation normal, reflection none
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) config/udev: removing device LITE-ON Technology USB NetVista Full Width Keyboard.
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) evdev: LITE-ON Technology USB NetVista Full Width Keyboard.: Close
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) UnloadModule: "evdev"
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (II) systemd-logind: releasing fd for 13:80
mei 20 12:44:48 lampje /usr/libexec/gdm-x-session[6428]: (EE) systemd-logind: failed to release device: Device not taken
mei 20 12:44:48 lampje gnome-settings-daemon.desktop[6059]: (gnome-settings-daemon:6059): color-plugin-WARNING **: failed to find device: property match 'XRANDR_name'='DisplayPort56' does not exist
mei 20 12:44:48 lampje pulseaudio[6016]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended.
mei 20 12:44:48 lampje kernel: thinkpad_acpi: EC reports that Thermal Table has changed
mei 20 12:44:49 lampje /usr/libexec/gdm-x-session[6428]: (II) intel(0): resizing framebuffer to 1920x1080
mei 20 12:44:49 lampje /usr/libexec/gdm-x-session[6428]: (II) intel(0): switch to mode 1920x1080 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
mei 20 12:44:56 lampje /usr/libexec/gdm-x-session[6428]: (II) AIGLX: Suspending AIGLX clients for VT switch

After this I can use my mouse and switch to other VTs, but the windows in X are drawn in incorrect places and don't respond to input. If I kill the X-server (for example through ctrl+alt+backspace) and log back in, then it works normal.

If I don't restart the X-server and just redock I see this:

mei 20 12:45:12 lampje kernel: thinkpad_acpi: docked into hotplug port replicator
mei 20 12:45:13 lampje gnome-settings-daemon.desktop[6733]: (gnome-settings-daemon:6733): color-plugin-WARNING **: no xrandr-Dell Inc.-DELL U2713HM-7JNY541PA46S device found: Failed to find output xrandr-Dell Inc.-DELL U2713HM-7JNY541PA46S
Comment 5 Sander Hoentjen 2016-05-30 09:04:04 UTC 
I was having the exact same issue, so I updated to F24 to see if that would solve the issue. So far it seems to be fine, but since it is an intermittent issue I cannot be sure yet. If I get another hang I will update the issue here but so far things look promising.
Comment 6 Sander Hoentjen 2016-05-30 09:05:41 UTC 
Oh for completeness:
kernel-4.5.5-300.fc24.x86_64
gnome-shell-3.20.2-1.fc24.x86_64
Comment 7 Sander Hoentjen 2016-06-03 10:35:44 UTC 
I can confirm this issue is solved for me with F-24, I haven't had the issue since updating.
Comment 8 Ewoud Kohl van Wijngaarden 2016-06-03 11:00:27 UTC 
I updated to kernel-4.5.5-201.fc23 from updates-testing and still had the issue. After upgrading to F24 my issue appears to be solved like Sander's.
Comment 9 Iiro Hietala 2016-06-29 07:35:23 UTC 
Another confirmation that this issue doesn't seem to occur anymore with F24 (4.5.7-300.fc24.x86_64) 

Laptop: Lenovo T460
Comment 10 Fedora End Of Life 2016-11-24 16:18:05 UTC 
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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.
Comment 11 Fedora End Of Life 2016-12-20 19:43:26 UTC 
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.