Had the same problem on Dell Latitude E6400 laptop using Gentoo Linux with udev versions newer than udev-233. Disabling Bluetooth in BIOS solved the issue, however, I need bluetooth. Researching the web resulted in this page:
Following the instructions mentioned by one user in the comments helped me to solve the cpu load issue with udev-239 and kernel 4.18.17, while Bluetooth still works.
Run the following command:
/lib/systemd/systemd-udevd -D
This should print garbage in endless loop containing ".../97-hid2hci.rules:"
If so, edit /lib/udev/rules.d/97-hid2hci.rules
and add
ACTION=="add",
in front of line mentioned by above command.
In my case, I had to change the following lines in 97-hid2hci.rules from:
Had the same problem on Dell Latitude E6400 laptop using Gentoo Linux with udev versions newer than udev-233. Disabling Bluetooth in BIOS solved the issue, however, I need bluetooth. Researching the web resulted in this page:
https:/ /askubuntu. com/questions/ 1028883/ ubuntu- 18-04-systemd- udevd-uses- high-cpu- conflict- with-wifi
Following the instructions mentioned by one user in the comments helped me to solve the cpu load issue with udev-239 and kernel 4.18.17, while Bluetooth still works.
Run the following command:
/lib/systemd/ systemd- udevd -D
This should print garbage in endless loop containing ".../97- hid2hci. rules:"
If so, edit /lib/udev/ rules.d/ 97-hid2hci. rules
and add
ACTION=="add",
in front of line mentioned by above command.
In my case, I had to change the following lines in 97-hid2hci.rules from:
ATTR{bInterface Class}= ="03", ATTR{bInterface SubClass} =="01", ATTR{bInterface Protocol} =="02", \ bDeviceClass} =="00", ATTRS{idVendor} =="413c" , ATTRS{bmAttribu tes}==" e0", \ SWITCH} ="1"
ATTRS{
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_
to:
ACTION=="add", ATTR{bInterface Class}= ="03", ATTR{bInterface SubClass} =="01", ATTR{bInterface Protocol} =="02", \ bDeviceClass} =="00", ATTRS{idVendor} =="413c" , ATTRS{bmAttribu tes}==" e0", \ SWITCH} ="1"
ATTRS{
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_
And this fixed the issue (after reboot).
Best regards
Florian