Ubuntu
linux package

System often freezes or panics if I log in with Dell Dock WD15 connected

Bug #1701499 reported by Piotr Kołaczkowski
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

I'm using Dell Precision 5520 with Ubuntu 17.04.

If I first start a Unity session and then connect Dell WD15 USB-C dock with an external diplay plugged in, the system detects it properly and all the things work flawlessly (ethernet, external keyboard, external display, external storage connected to USB on the dock). I can plug-in and plug-out the dock multiple times and it just works.

However if I boot the laptop with the dock already plugged in, first I get to the login screen and initially all is ok. Both screens are activated, and I can log in using the keyboard connected to the dock.

When I hit "Enter", both screens go blank for a while, then they turn back on and I can see the desktop. A second or maybe two seconds later things start falling apart. When I move the mouse pointer a second after logging, it is kinda "jumpy", the movement is not smooth. The move freezes for a few times. I observed this behaviour only when moving the wireless mouse connected to the USB of the laptop. The builtin touchpad works smoothly.

If it was the only issue, this would be a very minor annoyance. Sometimes, after a few short mouse pointer freezes the system starts working smoothly and all is rock stable from that point. However quite often I noticed much worse things happen:

1. The mouse pointer and everything freezes totally after a few seconds from displaying the desktop. It is not possible to switch to the console with Ctrl-Alt-F1. This happens in >50% of logins.

2. Kernel panic.

I observed this behavior with stable Ubuntu kernel 4.10.0-20, as well as 4.11.0 - 4.11.8 (which I'm using now, because 4.11.x seems more stable than 4.10.0-x) and also 4.12.rc5 which I tried once.

Even if everything goes fine, I noticed the following errors printed in syslog. I'm not sure if they are related, but they look very iffy to me:

Jun 30 10:46:23 p5520 kernel: [ 38.391971] DMAR: DRHD: handling fault status reg 2
Jun 30 10:46:23 p5520 kernel: [ 38.391977] DMAR: [INTR-REMAP] Request device [3e:00.0] fault index 1e [fault reason 38] Blocked an interrupt request due to source-id verification failure
Jun 30 10:46:23 p5520 kernel: [ 38.472490] xhci_hcd 0000:0a:00.0: remove, state 1
Jun 30 10:46:23 p5520 kernel: [ 38.472496] usb usb4: USB disconnect, device number 1
Jun 30 10:46:23 p5520 kernel: [ 38.472497] usb 4-1: USB disconnect, device number 2
Jun 30 10:46:23 p5520 kernel: [ 38.472498] usb 4-1.2: USB disconnect, device number 3
Jun 30 10:46:23 p5520 NetworkManager[1129]: <info> [1498812383.7510] device (eth0): state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Jun 30 10:46:23 p5520 ModemManager[1076]: <info> (net/eth0): released by modem /sys/devices/pci0000:00/0000:00:1d.6/0000:06:00.0/0000:07:02.0/0000:0a:00.0/usb4/4-1/4-1.2
Jun 30 10:46:23 p5520 NetworkManager[1129]: <info> [1498812383.7537] devices removed (path: /sys/devices/pci0000:00/0000:00:1d.6/0000:06:00.0/0000:07:02.0/0000:0a:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0, iface: eth0)
Jun 30 10:46:23 p5520 kernel: [ 38.552718] xhci_hcd 0000:0a:00.0: Host halt failed, -19
Jun 30 10:46:23 p5520 kernel: [ 38.552721] xhci_hcd 0000:0a:00.0: Host not accessible, reset failed.
Jun 30 10:46:23 p5520 kernel: [ 38.552722] xhci_hcd 0000:0a:00.0: USB bus 4 deregistered
Jun 30 10:46:23 p5520 kernel: [ 38.552728] xhci_hcd 0000:0a:00.0: remove, state 1
Jun 30 10:46:23 p5520 kernel: [ 38.552731] usb usb3: USB disconnect, device number 1
Jun 30 10:46:23 p5520 kernel: [ 38.552732] usb 3-1: USB disconnect, device number 2
Jun 30 10:46:23 p5520 kernel: [ 38.552732] usb 3-1.5: USB disconnect, device number 3
Jun 30 10:46:23 p5520 kernel: [ 38.553322] usb 3-1.7: USB disconnect, device number 4
Jun 30 10:46:23 p5520 kernel: [ 38.556064] BUG: unable to handle kernel paging request at 0000002018387ad8
Jun 30 10:46:23 p5520 kernel: [ 38.556173] IP: __radix_tree_lookup+0x10/0xf0
Jun 30 10:46:23 p5520 kernel: [ 38.556230] PGD 0
Jun 30 10:46:23 p5520 kernel: [ 38.556232]
Jun 30 10:46:24 p5520 kernel: [ 38.556280] Oops: 0000 [#1] SMP
Jun 30 10:46:24 p5520 kernel: [ 38.556320] Modules linked in: ccm rfcomm cdc_ether usbnet snd_usb_audio snd_usbmidi_lib r8152 mii snd_hda_codec_hdmi cmac msr uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media btusb btrtl joydev hid_multitouch ipmi_devintf ipmi_msghandler bnep nls_iso8859_1 arc4 dell_led snd_hda_codec_realtek snd_hda_codec_generic i2c_designware_platform i2c_designware_core dell_wmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi intel_rapl snd_seq_midi_event x86_pkg_temp_thermal snd_rawmidi intel_powerclamp coretemp kvm_intel kvm snd_seq irqbypass crct10dif_pclmul crc32_pclmul dell_rbtn ghash_clmulni_intel pcbc snd_seq_device dell_laptop snd_timer dell_smbios dcdbas iwlmvm dell_smm_hwmon mac80211 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd
Jun 30 10:46:24 p5520 kernel: [ 38.556557] swap_info_get: Bad swap offset entry 24000001b40
Jun 30 10:46:24 p5520 kernel: [ 38.556558] BUG: Bad page map in process systemd-udevd pte:90000006d00052 pmd:46463c067
Jun 30 10:46:24 p5520 kernel: [ 38.556559] addr:00007f4a83c00000 vm_flags:08000070 anon_vma: (null) mapping:ffff907a1afed288 index:27
Jun 30 10:46:24 p5520 kernel: [ 38.556563] file:libacl.so.1.1.0 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Jun 30 10:46:24 p5520 kernel: [ 38.556564] CPU: 0 PID: 3268 Comm: systemd-udevd Tainted: G U 4.11.8-041108-generic #201706290836
Jun 30 10:46:24 p5520 kernel: [ 38.556565] Hardware name: Dell Inc. Precision 5520/06X96V, BIOS 1.3.3 05/08/2017
Jun 30 10:46:24 p5520 kernel: [ 38.556565] Call Trace:
Jun 30 10:46:24 p5520 kernel: [ 38.556568] dump_stack+0x63/0x81
Jun 30 10:46:24 p5520 kernel: [ 38.556569] print_bad_pte+0x1df/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556571] ? __swap_info_get+0x5d/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556571] ? _swap_info_get+0x12/0x50
Jun 30 10:46:24 p5520 kernel: [ 38.556572] unmap_page_range+0x562/0x930
Jun 30 10:46:24 p5520 kernel: [ 38.556573] unmap_single_vma+0x7d/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556574] unmap_vmas+0x51/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556575] exit_mmap+0xa7/0x170
Jun 30 10:46:24 p5520 kernel: [ 38.556577] mmput+0x57/0x130
Jun 30 10:46:24 p5520 kernel: [ 38.556578] do_exit+0x295/0xb30
Jun 30 10:46:24 p5520 kernel: [ 38.556579] ? __secure_computing+0x3f/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556580] ? syscall_trace_enter+0xcd/0x2e0
Jun 30 10:46:24 p5520 kernel: [ 38.556581] do_group_exit+0x43/0xb0
Jun 30 10:46:24 p5520 kernel: [ 38.556582] SyS_exit_group+0x14/0x20
Jun 30 10:46:24 p5520 kernel: [ 38.556582] do_syscall_64+0x5b/0xc0
Jun 30 10:46:24 p5520 kernel: [ 38.556584] entry_SYSCALL64_slow_path+0x25/0x25
Jun 30 10:46:24 p5520 kernel: [ 38.556585] RIP: 0033:0x7f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556586] RSP: 002b:00007ffc965e0f98 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
Jun 30 10:46:24 p5520 kernel: [ 38.556587] RAX: ffffffffffffffda RBX: 00007ffc965e1060 RCX: 00007f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556587] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556587] RBP: 00007ffc965e1110 R08: 00000000000000e7 R09: fffffffffffffe50
Jun 30 10:46:24 p5520 kernel: [ 38.556588] R10: 00007f4a83129b50 R11: 0000000000000206 R12: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556588] R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
Jun 30 10:46:24 p5520 kernel: [ 38.556589] swap_info_get: Bad swap offset entry 180c001c0280
Jun 30 10:46:24 p5520 kernel: [ 38.556589] BUG: Bad page map in process systemd-udevd pte:603000700a00018 pmd:46463c067
Jun 30 10:46:24 p5520 kernel: [ 38.556590] addr:00007f4a83c01000 vm_flags:08000070 anon_vma: (null) mapping:ffff907a1afed288 index:28
Jun 30 10:46:24 p5520 kernel: [ 38.556592] file:libacl.so.1.1.0 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Jun 30 10:46:24 p5520 kernel: [ 38.556593] CPU: 0 PID: 3268 Comm: systemd-udevd Tainted: G BU 4.11.8-041108-generic #201706290836
Jun 30 10:46:24 p5520 kernel: [ 38.556593] Hardware name: Dell Inc. Precision 5520/06X96V, BIOS 1.3.3 05/08/2017
Jun 30 10:46:24 p5520 kernel: [ 38.556593] Call Trace:
Jun 30 10:46:24 p5520 kernel: [ 38.556594] dump_stack+0x63/0x81
Jun 30 10:46:24 p5520 kernel: [ 38.556595] print_bad_pte+0x1df/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556595] ? __swap_info_get+0x5d/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556596] ? _swap_info_get+0x12/0x50
Jun 30 10:46:24 p5520 kernel: [ 38.556597] unmap_page_range+0x562/0x930
Jun 30 10:46:24 p5520 kernel: [ 38.556598] unmap_single_vma+0x7d/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556599] unmap_vmas+0x51/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556600] exit_mmap+0xa7/0x170
Jun 30 10:46:24 p5520 kernel: [ 38.556601] mmput+0x57/0x130
Jun 30 10:46:24 p5520 kernel: [ 38.556602] do_exit+0x295/0xb30
Jun 30 10:46:24 p5520 kernel: [ 38.556602] ? __secure_computing+0x3f/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556603] ? syscall_trace_enter+0xcd/0x2e0
Jun 30 10:46:24 p5520 kernel: [ 38.556604] do_group_exit+0x43/0xb0
Jun 30 10:46:24 p5520 kernel: [ 38.556605] SyS_exit_group+0x14/0x20
Jun 30 10:46:24 p5520 kernel: [ 38.556605] do_syscall_64+0x5b/0xc0
Jun 30 10:46:24 p5520 kernel: [ 38.556606] entry_SYSCALL64_slow_path+0x25/0x25
Jun 30 10:46:24 p5520 kernel: [ 38.556607] RIP: 0033:0x7f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556607] RSP: 002b:00007ffc965e0f98 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
Jun 30 10:46:24 p5520 kernel: [ 38.556608] RAX: ffffffffffffffda RBX: 00007ffc965e1060 RCX: 00007f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556609] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556609] RBP: 00007ffc965e1110 R08: 00000000000000e7 R09: fffffffffffffe50
Jun 30 10:46:24 p5520 kernel: [ 38.556609] R10: 00007f4a83129b50 R11: 0000000000000206 R12: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556610] R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
Jun 30 10:46:24 p5520 kernel: [ 38.556610] BUG: Bad page map in process systemd-udevd pte:2800010000003333 pmd:46463c067
Jun 30 10:46:24 p5520 kernel: [ 38.556611] addr:00007f4a83c03000 vm_flags:08000070 anon_vma: (null) mapping:ffff907a1afed288 index:2a
Jun 30 10:46:24 p5520 kernel: [ 38.556613] file:libacl.so.1.1.0 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Jun 30 10:46:24 p5520 kernel: [ 38.556613] CPU: 0 PID: 3268 Comm: systemd-udevd Tainted: G BU 4.11.8-041108-generic #201706290836
Jun 30 10:46:24 p5520 kernel: [ 38.556613] Hardware name: Dell Inc. Precision 5520/06X96V, BIOS 1.3.3 05/08/2017
Jun 30 10:46:24 p5520 kernel: [ 38.556614] Call Trace:
Jun 30 10:46:24 p5520 kernel: [ 38.556614] dump_stack+0x63/0x81
Jun 30 10:46:24 p5520 kernel: [ 38.556615] print_bad_pte+0x1df/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556616] ? print_bad_pte+0x1ee/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556616] ? __swap_info_get+0x5d/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556617] vm_normal_page+0x90/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556618] unmap_page_range+0x576/0x930
Jun 30 10:46:24 p5520 kernel: [ 38.556619] unmap_single_vma+0x7d/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556619] unmap_vmas+0x51/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556620] exit_mmap+0xa7/0x170
Jun 30 10:46:24 p5520 kernel: [ 38.556622] mmput+0x57/0x130
Jun 30 10:46:24 p5520 kernel: [ 38.556622] do_exit+0x295/0xb30
Jun 30 10:46:24 p5520 kernel: [ 38.556623] ? __secure_computing+0x3f/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556624] ? syscall_trace_enter+0xcd/0x2e0
Jun 30 10:46:24 p5520 kernel: [ 38.556624] do_group_exit+0x43/0xb0
Jun 30 10:46:24 p5520 kernel: [ 38.556625] SyS_exit_group+0x14/0x20
Jun 30 10:46:24 p5520 kernel: [ 38.556626] do_syscall_64+0x5b/0xc0
Jun 30 10:46:24 p5520 kernel: [ 38.556627] entry_SYSCALL64_slow_path+0x25/0x25
Jun 30 10:46:24 p5520 kernel: [ 38.556627] RIP: 0033:0x7f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556627] RSP: 002b:00007ffc965e0f98 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
Jun 30 10:46:24 p5520 kernel: [ 38.556628] RAX: ffffffffffffffda RBX: 00007ffc965e1060 RCX: 00007f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556628] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556628] RBP: 00007ffc965e1110 R08: 00000000000000e7 R09: fffffffffffffe50
Jun 30 10:46:24 p5520 kernel: [ 38.556629] R10: 00007f4a83129b50 R11: 0000000000000206 R12: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556629] R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
Jun 30 10:46:24 p5520 kernel: [ 38.556631] swap_info_get: Bad swap file entry 1a0021837618faf6
Jun 30 10:46:24 p5520 kernel: [ 38.556631] BUG: Bad page map in process systemd-udevd pte:860dd863ebd9af8 pmd:46463c067
Jun 30 10:46:24 p5520 kernel: [ 38.556632] addr:00007f4a83c04000 vm_flags:08000070 anon_vma: (null) mapping:ffff907a1afed288 index:2b
Jun 30 10:46:24 p5520 kernel: [ 38.556633] file:libacl.so.1.1.0 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Jun 30 10:46:24 p5520 kernel: [ 38.556634] CPU: 0 PID: 3268 Comm: systemd-udevd Tainted: G BU 4.11.8-041108-generic #201706290836
Jun 30 10:46:24 p5520 kernel: [ 38.556634] Hardware name: Dell Inc. Precision 5520/06X96V, BIOS 1.3.3 05/08/2017
Jun 30 10:46:24 p5520 kernel: [ 38.556634] Call Trace:
Jun 30 10:46:24 p5520 kernel: [ 38.556635] dump_stack+0x63/0x81
Jun 30 10:46:24 p5520 kernel: [ 38.556635] print_bad_pte+0x1df/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556636] ? __swap_info_get+0x91/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556637] ? _swap_info_get+0x12/0x50
Jun 30 10:46:24 p5520 kernel: [ 38.556638] unmap_page_range+0x562/0x930
Jun 30 10:46:24 p5520 kernel: [ 38.556639] unmap_single_vma+0x7d/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556639] unmap_vmas+0x51/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556640] exit_mmap+0xa7/0x170
Jun 30 10:46:24 p5520 kernel: [ 38.556641] mmput+0x57/0x130
Jun 30 10:46:24 p5520 kernel: [ 38.556642] do_exit+0x295/0xb30
Jun 30 10:46:24 p5520 kernel: [ 38.556643] ? __secure_computing+0x3f/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556644] ? syscall_trace_enter+0xcd/0x2e0
Jun 30 10:46:24 p5520 kernel: [ 38.556645] do_group_exit+0x43/0xb0
Jun 30 10:46:24 p5520 kernel: [ 38.556646] SyS_exit_group+0x14/0x20
Jun 30 10:46:24 p5520 kernel: [ 38.556646] do_syscall_64+0x5b/0xc0
Jun 30 10:46:24 p5520 kernel: [ 38.556647] entry_SYSCALL64_slow_path+0x25/0x25
Jun 30 10:46:24 p5520 kernel: [ 38.556648] RIP: 0033:0x7f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556648] RSP: 002b:00007ffc965e0f98 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
Jun 30 10:46:24 p5520 kernel: [ 38.556648] RAX: ffffffffffffffda RBX: 00007ffc965e1060 RCX: 00007f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556649] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556649] RBP: 00007ffc965e1110 R08: 00000000000000e7 R09: fffffffffffffe50
Jun 30 10:46:24 p5520 kernel: [ 38.556649] R10: 00007f4a83129b50 R11: 0000000000000206 R12: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556649] R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
Jun 30 10:46:24 p5520 kernel: [ 38.556650] BUG: Bad page map in process systemd-udevd pte:80fe01111800c568 pmd:46463c067
Jun 30 10:46:24 p5520 kernel: [ 38.556651] addr:00007f4a83c05000 vm_flags:08000070 anon_vma: (null) mapping:ffff907a1afed288 index:2c
Jun 30 10:46:24 p5520 kernel: [ 38.556652] file:libacl.so.1.1.0 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Jun 30 10:46:24 p5520 kernel: [ 38.556653] CPU: 0 PID: 3268 Comm: systemd-udevd Tainted: G BU 4.11.8-041108-generic #201706290836
Jun 30 10:46:24 p5520 kernel: [ 38.556653] Hardware name: Dell Inc. Precision 5520/06X96V, BIOS 1.3.3 05/08/2017
Jun 30 10:46:24 p5520 kernel: [ 38.556653] Call Trace:
Jun 30 10:46:24 p5520 kernel: [ 38.556654] dump_stack+0x63/0x81
Jun 30 10:46:24 p5520 kernel: [ 38.556654] print_bad_pte+0x1df/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556655] ? print_bad_pte+0x1ee/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556656] ? __swap_info_get+0x91/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556656] vm_normal_page+0x69/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556657] unmap_page_range+0x576/0x930
Jun 30 10:46:24 p5520 kernel: [ 38.556658] unmap_single_vma+0x7d/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556659] unmap_vmas+0x51/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556660] exit_mmap+0xa7/0x170
Jun 30 10:46:24 p5520 kernel: [ 38.556661] mmput+0x57/0x130
Jun 30 10:46:24 p5520 kernel: [ 38.556661] do_exit+0x295/0xb30
Jun 30 10:46:24 p5520 kernel: [ 38.556662] ? __secure_computing+0x3f/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556663] ? syscall_trace_enter+0xcd/0x2e0
Jun 30 10:46:24 p5520 kernel: [ 38.556664] do_group_exit+0x43/0xb0
Jun 30 10:46:24 p5520 kernel: [ 38.556664] SyS_exit_group+0x14/0x20
Jun 30 10:46:24 p5520 kernel: [ 38.556665] do_syscall_64+0x5b/0xc0
Jun 30 10:46:24 p5520 kernel: [ 38.556666] entry_SYSCALL64_slow_path+0x25/0x25
Jun 30 10:46:24 p5520 kernel: [ 38.556666] RIP: 0033:0x7f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556666] RSP: 002b:00007ffc965e0f98 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
Jun 30 10:46:24 p5520 kernel: [ 38.556667] RAX: ffffffffffffffda RBX: 00007ffc965e1060 RCX: 00007f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556667] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556667] RBP: 00007ffc965e1110 R08: 00000000000000e7 R09: fffffffffffffe50
Jun 30 10:46:24 p5520 kernel: [ 38.556668] R10: 00007f4a83129b50 R11: 0000000000000206 R12: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556668] R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
Jun 30 10:46:24 p5520 kernel: [ 38.556669] swap_info_get: Bad swap offset entry be3c00000000
Jun 30 10:46:24 p5520 kernel: [ 38.556669] BUG: Bad page map in process systemd-udevd pte:2f8f000000000000 pmd:46463c067
Jun 30 10:46:24 p5520 kernel: [ 38.556670] addr:00007f4a83c06000 vm_flags:08000070 anon_vma: (null) mapping:ffff907a1afed288 index:2d
Jun 30 10:46:24 p5520 kernel: [ 38.556671] file:libacl.so.1.1.0 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Jun 30 10:46:24 p5520 kernel: [ 38.556671] CPU: 0 PID: 3268 Comm: systemd-udevd Tainted: G BU 4.11.8-041108-generic #201706290836
Jun 30 10:46:24 p5520 kernel: [ 38.556672] Hardware name: Dell Inc. Precision 5520/06X96V, BIOS 1.3.3 05/08/2017
Jun 30 10:46:24 p5520 kernel: [ 38.556672] Call Trace:
Jun 30 10:46:24 p5520 kernel: [ 38.556672] dump_stack+0x63/0x81
Jun 30 10:46:24 p5520 kernel: [ 38.556673] print_bad_pte+0x1df/0x2b0
Jun 30 10:46:24 p5520 kernel: [ 38.556674] ? __swap_info_get+0x5d/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556674] ? _swap_info_get+0x12/0x50
Jun 30 10:46:24 p5520 kernel: [ 38.556675] unmap_page_range+0x562/0x930
Jun 30 10:46:24 p5520 kernel: [ 38.556676] unmap_single_vma+0x7d/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556677] unmap_vmas+0x51/0xa0
Jun 30 10:46:24 p5520 kernel: [ 38.556678] exit_mmap+0xa7/0x170
Jun 30 10:46:24 p5520 kernel: [ 38.556679] mmput+0x57/0x130
Jun 30 10:46:24 p5520 kernel: [ 38.556680] do_exit+0x295/0xb30
Jun 30 10:46:24 p5520 kernel: [ 38.556680] ? __secure_computing+0x3f/0xe0
Jun 30 10:46:24 p5520 kernel: [ 38.556681] ? syscall_trace_enter+0xcd/0x2e0
Jun 30 10:46:24 p5520 kernel: [ 38.556682] do_group_exit+0x43/0xb0
Jun 30 10:46:24 p5520 kernel: [ 38.556682] SyS_exit_group+0x14/0x20
Jun 30 10:46:24 p5520 kernel: [ 38.556683] do_syscall_64+0x5b/0xc0
Jun 30 10:46:24 p5520 kernel: [ 38.556684] entry_SYSCALL64_slow_path+0x25/0x25
Jun 30 10:46:24 p5520 kernel: [ 38.556684] RIP: 0033:0x7f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556684] RSP: 002b:00007ffc965e0f98 EFLAGS: 00000206 ORIG_RAX: 00000000000000e7
Jun 30 10:46:24 p5520 kernel: [ 38.556685] RAX: ffffffffffffffda RBX: 00007ffc965e1060 RCX: 00007f4a82e35738
Jun 30 10:46:24 p5520 kernel: [ 38.556686] RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556686] RBP: 00007ffc965e1110 R08: 00000000000000e7 R09: fffffffffffffe50
Jun 30 10:46:24 p5520 kernel: [ 38.556686] R10: 00007f4a83129b50 R11: 0000000000000206 R12: 0000000000000000
Jun 30 10:46:24 p5520 kernel: [ 38.556687] R13: 0000000000000000 R14: 0000000000000003 R15: 000000000000000e
Jun 30 10:46:24 p5520 kernel: [ 38.556687] BUG: Bad page map in process systemd-udevd pte:2ff8f84e07df7c6 pmd:46463c067
Jun 30 10:46:24 p5520 kernel: [ 38.556688] addr:00007f4a83c07000 vm_flags:08000070 anon_vma: (null) mapping:ffff907a1afed288 index:2e
Jun 30 10:46:24 p5520 kernel: [ 38.556689] file:libacl.so.1.1.0 fault:ext4_filemap_fault mmap:ext4_file_mmap readpage:ext4_readpage
Jun 30 10:46:24 p5520 kernel: [ 38.556690] CPU: 0 PID: 3268 Comm: systemd-udevd Tainted: G BU 4.11.8-041108-generic #201706290836
---
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CurrentDesktop: Unity:Unity7
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-04-12 (78 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Package: linux (not installed)
Tags: zesty
Uname: Linux 4.11.8-041108-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

See original description
Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote : JournalErrors.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote : ProcEnviron.txt

apport information

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1701499

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

I did apport-collect immediately after filing the bug.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12

Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

Yesterday I updated to 4.11.9 and so far everything is stable. I managed to reboot 6 times in a row with no issues. The kernel error is also gone from syslog.

I'm still not totally sure, because the original issue is a bit random, so that might have been just a good luck.

The jumpiness of mouse pointer shortly after connecting the dock remained, but this is a very minor issue (and might not be related to the freeze / panic problems).

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

Unfortunately that turned out to be a fluke. I had two freezes on 4.11.12, and just a freeze a minute ago on fresh 4.13.rc3 installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/. No panics though.

I noticed all these freezes have a few things in common:
- they happen only when the dock is plugged in during logging into Ubuntu session; they don't happen if I plug in the dock after logging in.
- they happen AFTER the ethernet connection through the dock is dropped and BEFORE it is reestablished after login - when the freeze happens, the network manager shows I have only wifi connection. If the system goes past reestablishing ethernet connection through the dock, everything works smoothly. Also suspend/resume with the dock connected is fine.

Additionally, the dock seems to operate properly before I login. I never ever had a panic or freeze before logging into my account. The network manager icon shows the ethernet connection is active at the login screen. However, this connection is dropped immediately after logging in (why?) and re-established.

I also noticed some rare instabilities in ethernet connectivity - sometimes it just drops the connection in the middle of the day and needs replugging (reconnecting from network manager doesn't work in this case).

BTW: I updated the dock firmware to the most recent version from Dell. I had to use Windows for that. But this didn't help.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please file an upstream bug at [1], or escalate the issue to linux-usb mailing list [2].

[1] https://bugzilla.kernel.org/
[2] <email address hidden>

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

Tried posting to linux-usb mailing list but I got no answer back. Any other ways to report this problem?

The problem still exists with kernels 4.13.2 and 4.12.13.
I updated BIOS to 1.5.0 released today and also applied a fresh firmware update to WD15 from Dell (using Windows, because Linux can't do it yet) - and also no visible improvement.

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

Also, I've read this on another USB ticket in bugzilla:
All USB bugs should be sent to the <email address hidden> mailing
list, and not entered into bugzilla. Please bring this issue up there,
if it is still a problem in the latest kernel release.

So it looks like the mailing list is the only way.
Is it normal that I post something to the mailing list and get no answer back?

Revision history for this message
Mario Limonciello (superm1) wrote : Re: [Bug 1701499] Re: System often freezes or panics if I log in with Dell Dock WD15 connected

Can you please check if you're on the latest firmware for the 5520? There
was a recent issue on many laptops that was leading to instability
specifically with USB. BIOS has been released for many of them already.

On Fri, Sep 15, 2017, 10:36 Piotr Kołaczkowski <email address hidden> wrote:

> Also, I've read this on another USB ticket in bugzilla:
> All USB bugs should be sent to the <email address hidden> mailing
> list, and not entered into bugzilla. Please bring this issue up there,
> if it is still a problem in the latest kernel release.
>
>
> So it looks like the mailing list is the only way.
> Is it normal that I post something to the mailing list and get no answer
> back?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1701499
>
> Title:
> System often freezes or panics if I log in with Dell Dock WD15
> connected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701499/+subscriptions
>

Revision history for this message
Mario Limonciello (superm1) wrote :

From what I can tell you're on BIOS 1.3.3. Please upgrade to 1.5.0. It's available both for Ubuntu through fwupd (https://fwupd.org/lvfs/device/34578c72-11dc-4378-bc7f-b643866f598c) or can be updated from the F12 post menu by downloading from support.dell.com (https://www.dell.com/support/article/us/en/19/sln171755/updating-the-dell-bios-in-linux-and-ubuntu-environments?lang=en#updatebios2015)

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

I upgraded to BIOS 1.5.0 yesterday and also upgraded the dock firmware yesterday as well again (using windows-10-on-the-go usb stick I created just for that purpose).

No improvements - I got a nice freeze on boot again (kernel 4.12.13).

Also, Windows 10 seems to be working on the same hardware just fine; no freezes when booting with the dock plugged in, neither when hotplugging.

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

I can confirm 1.5.0:

Sep 15 12:00:22 p5520 kernel: [ 0.000000] DMI: Dell Inc. Precision 5520/06X96V, BIOS 1.5.0 08/30/2017

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :
Download full text (5.3 KiB)

Also, what are these dots in syslog?

Sep 15 09:55:14 p5520 kernel: [ 21.539677] hid-generic 0003:046D:C31F.0005: input,hiddev1,hidraw4: USB HID v1.10 Device [Logitech USB Keyboard] on usb-0000:3e:00.0-1.7/input1
Sep 15 09:55:14 p5520 mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1d.6/0000:06:00.0/0000:07:02.0/0000:3e:00.0/usb3/3-1/3-1.7"
Sep 15 09:55:14 p5520 mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1d.6/0000:06:00.0/0000:07:02.0/0000:3e:00.0/usb3/3-1/3-1.5"
Sep 15 09:55:14 p5520 mtp-probe: bus: 3, device: 4 was not an MTP device
Sep 15 09:55:14 p5520 mtp-probe: bus: 3, device: 3 was not an MTP device
Sep 15 09:55:14 p5520 kernel: [ 21.595628] usbcore: registered new interface driver r8152
Sep 15 09:55:14 p5520 kernel: [ 21.606763] usbcore: registered new interface driver cdc_ether
Sep 15 09:55:14 p5520 kernel: [ 21.683476] usb 4-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
Sep 15 09:55:14 p5520 kernel: [ 21.706117] r8152 4-1.2:1.0 (unnamed net_device) (uninitialized): Using pass-thru MAC addr d4:81:d7:35:8c:11
Sep 15 09:55:14 p5520 NetworkManager[1160]: <info> [1505462114.7966] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4)
Sep 15 09:55:14 p5520 kernel: [ 21.759684] r8152 4-1.2:1.0 eth0: v1.08.9
Sep 15 09:55:14 p5520 NetworkManager[1160]: <info> [1505462114.8162] devices added (path: /sys/devices/pci0000:00/0000:00:1d.6/0000:06:00.0/0000:07:02.0/0000:3e:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
 iface: eth0)
Sep 15 09:55:14 p5520 NetworkManager[1160]: <info> [1505462114.8162] device added (path: /sys/devices/pci0000:00/0000:00:1d.6/0000:06:00.0/0000:07:02.0/0000:3e:00.0/usb4/4-1/4-1.2/4-1.2:1.0/net/eth0,
iface: eth0): no ifupdown configuration found.
Sep 15 09:55:14 p5520 NetworkManager[1160]: <info> [1505462114.8175] device (eth0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Sep 15 09:55:14 p5520 kernel: [ 21.783371] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 15 09:55:14 p5520 kernel: [ 21.812778] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 15 09:55:15 p5520 kernel: [ 22.941812] usbcore: registered new interface driver snd-usb-audio
Sep 15 09:55:15 p5520 systemd-udevd[2621]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
Sep 15 09:55:16 p5520 pulseaudio[2115]: [pulseaudio] alsa-util.c: Unable to load mixer: Zły argument
Sep 15 09:55:16 p5520 pulseaudio[2115]: [pulseaudio] sink.c: Default and alternate sample rates are the same.
Sep 15 09:55:16 p5520 rtkit-daemon[2118]: Supervising 0 threads of 0 processes of 1 users.
Sep 15 09:55:16 p5520 rtkit-daemon[2118]: message repeated 4 times: [ Supervising 0 threads of 0 processes of 1 users.]
Sep 15 09:55:16 p5520 pulseaudio[2115]: [pulseaudio] alsa-util.c: Unable to load mixer: Zły argument
Sep 15 09:55:16 p5520 pulseaudio[2115]: [pulseaudio] source.c: Default and alternate sample rates are the same.
Sep 15 09:55:16 p5520 rtkit-daemon[2118]: Supervising 0 threads of 0 processes of 1 users.
Sep 15 09:55:16 p5520 rtkit-daemon[2118]: message repeated 4 times: [ Supervising 0 threads of 0 processes of 1...

Read more...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you try v4.14-rc1?
There are some fixes about iommu, thunderbolt, ACPI, etc.

If v4.14-rc1 doesn't work, we may need someone from Intel to check it.

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :
Download full text (7.3 KiB)

I was running v4.14-rc1 for the whole last week.
It is... different.

Good stuff:
- Not a single freeze on fresh boot with dock attached.
- When it connects to eth0, it is stable. Not a single disconnect from ethernet, but that may be as well the result of recent BIOS upgrade to 1.5.0 and dock firmware update that I did at about the time I upgraded to v4.14-rc1.
- Suspend / resume stable, as long as I don't connect/disconnect the dock in the meantime.

Slightly broken stuff:
- Ethernet connection does not come up automatically after boot / login. Syslog shows the eth0 device exists, NetworkManager attempts to connect, it even gets the IP from DHCP, then it suddenly disconnects. I have to manually click in the NetworkManager icon to connect after logging into desktop and suprisingly it connects fine.

Relevant syslog fragment:
Sep 17 11:43:17 p5520 kernel: [ 12.053069] usbcore: registered new
interface driver r8152
Sep 17 11:43:17 p5520 kernel: [ 12.055853] usbcore: registered new
interface driver cdc_ether
Sep 17 11:43:17 p5520 tlp[1907]: Applying power save settings...done.
Sep 17 11:43:17 p5520 tlp[1907]: Setting battery charge thresholds...done.
Sep 17 11:43:17 p5520 systemd[1]: Started TLP system startup/shutdown.
Sep 17 11:43:17 p5520 systemd[1]: Startup finished in 10.048s (kernel)
+ 2.022s (userspace) = 30.839s.
Sep 17 11:43:17 p5520 set-cpufreq[1209]: Setting powersave scheduler
for all CPUs
Sep 17 11:43:17 p5520 kernel: [ 12.136372] usb 4-1.2: reset
SuperSpeed USB device number 3 using xhci_hcd
Sep 17 11:43:17 p5520 kernel: [ 12.265293] r8152 4-1.2:1.0 (unnamed
net_device) (uninitialized): Using pass-thru MAC addr
d4:81:d7:35:8c:11
Sep 17 11:43:17 p5520 NetworkManager[1189]: <info> [1505641397.3556]
manager: (eth0): new Ethernet device
(/org/freedesktop/NetworkManager/Devices/2)
Sep 17 11:43:17 p5520 kernel: [ 12.297452] r8152 4-1.2:1.0 eth0: v1.09.9
...
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7031]
device (eth0): link connected
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7043]
device (eth0): state change: unavailable -> disconnected (reason
'carrier-changed') [20 30 40]
Sep 17 11:43:20 p5520 kernel: [ 15.645145] r8152 4-1.2:1.0 eth0: carrier on
Sep 17 11:43:20 p5520 kernel: [ 15.645217] IPv6:
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7056]
policy: auto-activating connection 'Połączenie ethernetowe 1'
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7078]
device (eth0): Activation: starting connection 'Połączenie ethernetowe
1' (e6a365af-c48e-4b8f-abd0-1ee3ea9f1a7b)
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7081]
device (eth0): state change: disconnected -> prepare (reason 'none')
[30 40 0]
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7089]
device (eth0): state change: prepare -> config (reason 'none') [40 50
0]
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7095]
device (eth0): state change: config -> ip-config (reason 'none') [50
70 0]
Sep 17 11:43:20 p5520 NetworkManager[1189]: <info> [1505641400.7101]
dhcp4 (eth0): activation: ...

Read more...

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

I also checked 4.13.3 a moment ago and when booting with the dock attached I got a freeze again soon after starting the desktop session. So the original bug I reported here was definitely not fixed in 4.13.3, nor by BIOS upgrade to 1.5.0. However, all network connections were active at the login screen.

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

Still using 4.13.3 today and I already had sudden ethernet connection dropout which couldn't be reestabliished from NetworkManager without replugging the dock. I conclude this problem must be related to kernel then, because as said earlier, on 4.14.rc1 I had no ethernet stability issues for the whole week (besides having to manually establish it after logging).

I have pretty high hopes for 4.14.x then as it seems to fix the two most serious issues.
What a pity that 4.14.rc2 doesn't work for me at all :(

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :
Download full text (4.6 KiB)

just FYI: 4.14.rc2 networking failure seems to be caused by dhcp client crash. Where to submit bug report for this?

Sep 25 21:07:47 p5520 nm-applet[3178]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: SME: Trying to authenticate with 90:5c:44:98:88:43 (SSID='UPCFB73B8F' freq=5500 MHz)
Sep 25 21:07:48 p5520 kernel: [ 87.302852] wlp2s0: authenticate with 90:5c:44:98:88:43
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.3216] device (wlp2s0): supplicant interface state: scanning -> authenticating
Sep 25 21:07:48 p5520 kernel: [ 87.309769] wlp2s0: send auth to 90:5c:44:98:88:43 (try 1/3)
Sep 25 21:07:48 p5520 nm-applet[3178]: Can't set a parent on widget which has a parent
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: Trying to associate with 90:5c:44:98:88:43 (SSID='UPCFB73B8F' freq=5500 MHz)
Sep 25 21:07:48 p5520 kernel: [ 87.332279] wlp2s0: authenticated
Sep 25 21:07:48 p5520 kernel: [ 87.333039] wlp2s0: associating with AP with corrupt probe response
Sep 25 21:07:48 p5520 kernel: [ 87.336133] wlp2s0: associate with 90:5c:44:98:88:43 (try 1/3)
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.3494] device (wlp2s0): supplicant interface state: authenticating -> associating
Sep 25 21:07:48 p5520 nm-applet[3178]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Sep 25 21:07:48 p5520 kernel: [ 87.374203] wlp2s0: RX AssocResp from 90:5c:44:98:88:43 (capab=0x511 status=0 aid=2)
Sep 25 21:07:48 p5520 kernel: [ 87.376217] wlp2s0: associated
Sep 25 21:07:48 p5520 nm-applet[3178]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: Associated with 90:5c:44:98:88:43
Sep 25 21:07:48 p5520 kernel: [ 87.376544] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.3949] device (wlp2s0): supplicant interface state: associating -> associated
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.4180] device (wlp2s0): supplicant interface state: associated -> 4-way handshake
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: WPA: Key negotiation completed with 90:5c:44:98:88:43 [PTK=CCMP GTK=CCMP]
Sep 25 21:07:48 p5520 wpa_supplicant[1521]: wlp2s0: CTRL-EVENT-CONNECTED - Connection to 90:5c:44:98:88:43 completed [id=0 id_str=]
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.4255] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.4257] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'UPCFB73B8F'.
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.4260] device (wlp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.4278] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 25 21:07:48 p5520 NetworkManager[1133]: <info> [1506366468.4354] dhcp4 (wlp2s0): dhclient started with pid 3528
Sep 25 21:07:48 p5520 kernel: [...

Read more...

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

4.14.rc2 network problem fixed by running:

sudo ln -s /etc/apparmor.d/sbin.dhclient /etc/apparmor.d/disable/
sudo /etc/init.d/apparmor reload

Now I can use 4.14.rc2 and will let you know how stable it is.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

That's probably some AppArmor regression introduced in v4.14-rc2.

Do you still see "Severely broken stuffs" on v4.14-rc2?

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

No, after disabling apparmor for dhclient, I'm successfully running v4.14-rc2.
However, it looks like exactly the same problems exist with this kernel as with v4.14-rc2:

1. NetworkManager fails to connect automatically at startup, but connects fine after manual intervention.

2. System fails to resume if it was disconnected from the dock while suspended.

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

After a week of testing v4.14-rc2, the conclusions remain the same:
- System doesn't freeze when booting up and logging in with the dock attached.
- Ethernet doesn't connect automatically on boot / after login, manual intervention required.
- System doesn't wake from suspend if the dock was disconnected during sleep.
- System does wake properly from suspend if the dock was connected during sleep or dock connection did not change at all.
- No sudden ethernet disconnects.

I've got also a TB16 dock now:
Problems with kernel 4.13.4:
- Graphics crash when booting with dock attached, Ubuntu displayed a message asking what to do, but it recovered after selecting low res mode. Interestingly, I managed to log into desktop.
- Everything else same as with WD15 dock.

Kernel v4.14.rc2: same behavior as with v4.14.rc2 + WD15 dock.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

I can reproduce the issue on latest Artful release. Although I use XPS 9360 instead of Precision 5520. The kernel is 4.13 based.

I'll try finding a Precision 5520.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Uh, I meant "I cannot reproduce the issue".

Revision history for this message
Mario Limonciello (superm1) wrote :

There was a problem I found a little while back with hooking up dock to
artful where gnome would crash. That was fixed recently, but I haven't seen
anything else either (both wd15 and tb16 with XPS 9350)

On Thu, Oct 19, 2017, 23:15 Kai-Heng Feng <email address hidden>
wrote:

> Uh, I meant "I cannot reproduce the issue".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1701499
>
> Title:
> System often freezes or panics if I log in with Dell Dock WD15
> connected
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701499/+subscriptions
>

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Yea, I think it's related to gnome-shell.

Piotr, can you enable persistent journal for journald?

$ sudo -s
# mkdir -p /var/log/journal
# systemd-tmpfiles --create --prefix /var/log/journal
# systemctl restart systemd-journald

If your computer freeze again, you can use
$ journalctl -b -1
to check the log from last boot. Check if you can see some warning about gnome-shell.

Revision history for this message
Mario Limonciello (superm1) wrote :

Here's more detail, the gnome-shell fix came with this bug:
https://launchpad.net/bugs/1722811

The apparmor problem with 4.14 is described here:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278

So please do share if you're encountering issues after upgrading to that newer version of mutter (including what version is on your system).

Revision history for this message
Piotr Kołaczkowski (pkolaczk-u) wrote :

Unfortunately I no longer have the WD15 dock. I switched to TB16 and it also has some hotplugging issue (there is a separate launchpad ticket reported by others).

Brad Figg (brad-figg)
tags: added: cscc
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.