Launchpad has imported 7 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=199035.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2018-03-06T21:09:45+00:00 mathieutournier wrote: Created attachment 274593 dmesg Hi, I'm currently running ubuntu 18.04 with a 4.15 kernel and i can observe very high cpu usage to the systemd-udevd deamon. removing the rule : 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" Solved the high CPU usage eventhough my bluetooth card is not available anymore (as not in hci mode) It seems that the command hid2hci creates a bind/unbind loop in udev that is looping trying to set the device in hci mode. (that what udevadm monitor seems to show, looping from bind to unbind for the device) I suspect a0085f2510e8976614ad8f766b209448b385492f introduced a regression (i have not tried to revert it yet). Please not that there also seem to be a bug in hid2hci.c from bluez l148 : if (err == 0) { err = -1; errno = EALREADY; } Correcting this and recompile bluez desn't solve the issue as cpu usage remains very high. Using a 4.13 kernel result in a normal CPU usage, this seems a regression in 4.14. Other people seems to have the same issue, here is a bug report related to this : https://dev.solus-project.com/T5224 Thanks a lot for your support, Mathieu Tournier Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/0 ------------------------------------------------------------------------ On 2018-05-04T05:57:10+00:00 boro wrote: I have the very same problem using the same distro (Ubuntu 18.04, 64-bit) on Dell Latitude E5400 laptop. Disabling BT from BIOS or removing the aforementioned rule solves the problem but leaves BT unusable. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/13 ------------------------------------------------------------------------ On 2018-05-09T23:02:06+00:00 lucent wrote: Bus 001 Device 009: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 004: ID 0a5c:0000 Broadcom Corp. Linux zontar 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29) x86_64 GNU/Linux May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0 May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0 May 09 15:59:00 hostname upowerd[14610]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0 May 09 15:59:00 hostname upowerd[14610]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6.2/1-1.6.2:1.0 ...repeating... 15632 root 20 0 233136 186656 2664 R 94.1% 4.7% 62:14.67 systemd-udevd 16222 root 20 0 88252 2432 1888 R 35.3% 0.1% 25:21.87 systemd-udevd Looks like same problem affects this Dell Precision M6500 laptop. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/15 ------------------------------------------------------------------------ On 2018-05-20T07:57:41+00:00 f.dittmer wrote: I observed the high cpu usage after upgrading from udev-233 to udev-236/udev-238 on Gentoo Linux. Downgrading back to udev-233 lets me use newer kernels (currently running 4.15.18) without any problems. Using DELL Latitude E6400 from 2009, with same Broadcom Bluetooth module as mentioned above. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/27 ------------------------------------------------------------------------ On 2018-06-13T16:50:40+00:00 rickfharris wrote: As per https://patchwork.kernel.org/patch/10384111/ editing 97-hid2hci.rules as follows works around the new uevents added to the kernel in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65 -ACTION=="remove", GOTO="hid2hci_end" +ACTION!="add", GOTO="hid2hci_end" Bluetooth now works with kernels above and below 4.14. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/40 ------------------------------------------------------------------------ On 2018-06-14T00:32:13+00:00 rickfharris wrote: Scratch that last comment, on further testing found I was booted into incorrect kernel :/ Editing of 97-hid2hci.rules is not a solution. Only surefire way of getting bluetooth back and working with kernels >=4.14, was to revert the bogus kernel commit that added the bind/unbind uevents. Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/42 ------------------------------------------------------------------------ On 2018-06-14T00:33:52+00:00 rickfharris wrote: Created attachment 276537 revert-bind_unbind-uevents.patch Reply at: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836/comments/43 ** Changed in: bluez Status: Unknown => Confirmed ** Changed in: kernel Status: Unknown => Confirmed ** Changed in: bluez Importance: Unknown => High ** Changed in: kernel Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
