Kernel does not detect already connected USB devices on boot

[Jan Henke]

The kernel does not always detect already connected USB devices on boot. I have an USB nic and an external mouse connected to my Laptop. Sometimes these devices are recognized after boot, sometimes they are missing.

When they are not present after boot you have to unplug them and plug them again. This is inconvient and adds physical wear on the USB connectors.
The kernel log shows no sign of a disconnect, so it seems the kernel does not recognize the devices as plugged in on boot.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-9-generic 3.19.0-9.9
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D0p: jan 1733 F...m pulseaudio
 /dev/snd/controlC1: jan 1733 F.... pulseaudio
 /dev/snd/controlC0: jan 1733 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sun Mar 22 17:07:16 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-30 (50 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Dell Inc. XPS 13 9343
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic.efi.signed root=UUID=e4431ecc-e85e-4e35-92af-58f455c46c2b ro kvm-intel.nested=1 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-9-generic N/A
 linux-backports-modules-3.19.0-9-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago)
dmi.bios.date: 03/12/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd03/12/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.0-rc5-vivid/

[Jan Henke (jhe)]

The issue first happened after upgrading to vivid from utopic. The utopic kernel did not show this behaviour.

I did a short test with the upstream kernel and the issue could not be reproduced with it. Booting back into the Ubuntu kernel 3.19.0-9 on the other hand exhibited this issue again.

[Joseph Salisbury (jsalisbury)]

Can you also test the latest 3.19 upstream stable kernel? This will tell us if the fix in 4.0-rc5 was also sent for inclusion in the stable releases. It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.3-vivid/

[Jan Henke (jhe)]

I am currently running on 3.19.3 upstream and the bug did not occur. But I have to point out that the bug only occurred sometimes with the latest Ubuntu vivid kernel. I do not know yet how to reliably trigger this bug, it seems it needs some special conditions to happen.

[Jan Henke (jhe)]

I happened again after rebooting the first time into the 3.19.0-14 kernel yesterday. So it is not solved yet.

[Simon Repp (simonrepp)]

Hi,

I freshly installed 15.04 about a week ago (my kernel is 19.0-22-generic) and am experiencing similiar behaviour, with some additional symptoms to those described already:

- When the problem occurs for me, startup time spent on the loading screen ("colored dots") goes up from less than a second to about 1+ minute
- When the login screen is finally reached, I am not able to do anything (except cut power and hope it does not occur on the next boot) because un- and re-plugging any usb devices does nothing at all (my keyboard gets power, but is not recognized, same for mouse)

If I can provide any additional info to help with this, please let me know. Just like jhe, I didn't yet see any logic regarding how this problem is triggered so far.

[Simon Repp (simonrepp)]

I cannot speak for the bug opener, but for me this bug has been resolved (or it resolved itself otherwise, don't know). So you can safely ignore my previous post from now. :)

[AmiG (ami-geva)]

I'm using 14.04.3 on Dell XPS 13. I just updated the kernal to 3.19 as recommended on Dell's forum to try and solve my issue with the wifi not turning on after suspend. I didn't have any boot issues with the connected USBs (yet) but I did noticed an issue after returning from suspend. Hope this helps in debugging this issue.

[AmiG (ami-geva)]

An update: After some time, working, the usb mouse freezes from time to time. I return to 3.13 :(

[abadger (dave-netfm)]

I have a Huawei usb dongle and after a power cycle reboot all appears good:-

dave@withycombe:~$ uname -a
Linux withycombe 4.4.0-30-generic #49-Ubuntu SMP Thu Jun 30 20:51:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

dave@withycombe:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04 LTS
Release: 16.04
Codename: xenial

dave@withycombe:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 12d1:155e Huawei Technologies Co., Ltd.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dave@withycombe:~$ ls -l /dev/ttyU*
crw-rw---- 1 root dialout 188, 0 Jul 12 09:07 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Jul 12 09:07 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Jul 12 09:08 /dev/ttyUSB2
dave@withycombe:~$

However if I issue the command 'sudo reboot' then look at the system I don't get the /dev/ttyU* devices created. To be honest this bug is also complicated by fact that my Intel NUC computer does not always come back after a reboot. But that's a separate issue.

[abadger (dave-netfm)]

Now I did another 'power cycle..and the devices are not there ?'

dave@withycombe:~$ ls -l /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory
dave@withycombe:~$ ls -l /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory
dave@withycombe:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 12d1:1f01 Huawei Technologies Co., Ltd. E353/E3131 (Mass storage mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dave@withycombe:~$ ls -l /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory
dave@withycombe:~$ uptime
 09:18:14 up 0 min, 1 user, load average: 0.60, 0.23, 0.08
dave@withycombe:~$

[abadger (dave-netfm)]

dave@withycombe:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 12d1:1f01 Huawei Technologies Co., Ltd. E353/E3131 (Mass storage mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dave@withycombe:~$
dave@withycombe:~$
dave@withycombe:~$
dave@withycombe:~$ ls -l /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory
dave@withycombe:~$ ls -l /dev/ttyU*
ls: cannot access '/dev/ttyU*': No such file or directory *** Now unplug repliug donlge ***
dave@withycombe:~$ ls -l /dev/ttyU*
crw-rw---- 1 root dialout 188, 0 Jul 12 09:20 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Jul 12 09:20 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Jul 12 09:20 /dev/ttyUSB2
dave@withycombe:~$