Sometimes I am getting this message when the booting process starts:
1.745397] ehci-pci 0000:00:1a.0: can't setup: -110
1.745475] ehci-pci 0000:00:1a.0: init 0000:00:1a.0 fail, -110
And every time it appears my mouse doesn’t work (even the LED is off). This cable connection is: Monitor connected to the USB port and the mouse plugged in the monitor. This has worked for years without problems. However after a recent reinstall it started happening sometimes. The only new thing is that I installed using UEFI/GPT setup and the mother board firmware is updated to the latest. Interestingly when the mouse is plugged directly into a USB port of the PC this doesn’t happen. But I plug it in the monitor (which has 2 USB ports for devices) because all my USB ports are occupied by other devices.
USB mouse (Logitech M100) in case that matters.
I don’t know how to re-activate the mouse when this happens, so I reboot from console.
When booted normally and I grep the dmesg I see:
0.936493] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
0.936499] ehci-pci: EHCI PCI platform driver
0.936586] ehci-pci 0000:00:1a.0: EHCI Host Controller
0.936590] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
0.936601] ehci-pci 0000:00:1a.0: debug port 2
0.940503] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
0.940514] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7634000
0.946031] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
0.946059] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
0.946060] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
0.946061] usb usb1: Product: EHCI Host Controller
0.946062] usb usb1: Manufacturer: Linux 3.16.7-24-desktop ehci_hcd
0.946063] usb usb1: SerialNumber: 0000:00:1a.0
0.946144] hub 1-0:1.0: USB hub found
0.946149] hub 1-0:1.0: 2 ports detected
In UEFI/BIOS I have:
Intel USB2.0 EHCI Controller = Enabled
Legacy USB Support = Enabled
Legacy USB3.0 Support = Enabled
Intel xHCI Mode = Smart Auto
EHCI Hand-off = Disabled
The MB is ASUS P8Z77-V with latest firmware.
What might the problem be?