clauded
Posts: 44
Joined: Thu Jan 05, 2017 10:49 pm

High cpu usage and no bluetooth mouse with kernel 4.14

Fri Dec 08, 2017 8:17 pm

Just upgraded to 4.14 kernel. My bluetooth mouse don't work anymore and I have high cpu usage (systemd-udevd is using 25% of the cpu).

Log is filled with:

Code: Select all

déc 08 19:12:00 dell-laptop systemd-udevd[406]: Process 'hid2hci --method=dell --devpath=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/>
déc 08 19:12:00 dell-laptop upowerd[1841]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2>

Code: Select all

lsusb | grep Bluetooth
Bus 002 Device 010: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card
Bus 002 Device 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Reverting back to 4.13 and usb mouse works fine.

clauded
Posts: 44
Joined: Thu Jan 05, 2017 10:49 pm

Re: High cpu usage and no bluetooth mouse with kernel 4.14

Sun Dec 10, 2017 3:50 am

I also noticed a memory leak by systemd-udevd and these messages just keep reappearing in the logs:

déc 09 21:28:12 dell-laptop systemd-udevd[399]: Process 'hid2hci --method=dell --devpath=/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0' failed with exit code 1.
déc 09 21:28:12 dell-laptop upowerd[1890]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6.2/2-1.6.2:1.0

So as a work around, I did the following :

1-Copy 97-hid2hci.rules :
cp /usr/lib/udev/rules.d/97-hid2hci.rules /etc/udev/rules.d/

2- Remove those lines in /etc/udev/rules.d/97-hid2hci.rules:
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", ATTRS{bmAttributes}=="e0", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

3- Reboot.

Now I lost my bluetooth adaptor but no more high cpu usage and memory leak with 4.14.

clauded
Posts: 44
Joined: Thu Jan 05, 2017 10:49 pm

Re: High cpu usage and no bluetooth mouse with kernel 4.14

Mon Dec 11, 2017 12:02 am

I posted a temporary workaround here until the bug is fixed: https://dev.solus-project.com/T5224

Return to “Hardware”