You are not logged in.

#1 2017-12-22 03:29:23

jdoggsc
Member
Registered: 2011-08-15
Posts: 90

systemd-udevd using all CPU. Suspected errors caused by usb port

I'm going to try to describe my problem without being too wordy.  That way people will hopefully read this and offer help.
My laptop (Dell Latitude E6500)  has had the CPU pegged recently by systemd-udevd

my journalctl output is inundated with this, repeating at clock speed, of course, to maximize processor usage

Dec 21 21:55:00 jdoggsc systemd-udevd[7754]: Process 'hid2hci --method=dell --devpath=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0' failed with exit code 1.

It looks like systemd-udevd doesn't know how to handle this device.  From my experience, hci is associated with bluetooth (hciconfig...)  What is the connection with usb?  When I toggle the hardware switch on my laptop to disable radios, systemd-udevd stops freaking out, the messages disappear, and I processor usage goes back to idle.

I know I broke a usb port on my laptop about 2 years ago, but never had problems with it until recently.  Thinking this might be the problem, I tried to disable it as described in this thread, but the output of

# echo suspend | sudo tee /sys/bus/usb/devices/3-1.2\:1.0/power/level

is

 
tee: '/sys/bus/usb/devices/3-1.2:1.0/power/level': Permission denied

and

# echo suspend | sudo tee /sys/bus/usb/devices/3-1.2/power/level

yields

tee: /sys/bus/usb/devices/3-1.2/power/level: Invalid argument

Why does this USB device disappear when I disable the radio ?  This is how the contents of /sys/bus/usb/devices changes when the radio is off and then it is toggled on again

radios toggled off

lrwxrwxrwx 1 root root 0 Dec 19 22:32 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.7/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 2-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.7/usb2/2-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 3-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 4-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.1/usb4/4-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 5-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-0:1.0
lrwxrwxrwx 1 root root 0 Dec 21 21:24 5-1 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-1
lrwxrwxrwx 1 root root 0 Dec 21 21:24 5-1:0.0 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:0.0
lrwxrwxrwx 1 root root 0 Dec 21 21:24 5-1:0.1 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:0.1
lrwxrwxrwx 1 root root 0 Dec 19 22:32 6-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.0/usb6/6-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 7-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.1/usb7/7-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 8-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.2/usb8/8-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb1 -> ../../../devices/pci0000:00/0000:00:1a.7/usb1
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb2 -> ../../../devices/pci0000:00/0000:00:1d.7/usb2
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb3 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb4 -> ../../../devices/pci0000:00/0000:00:1a.1/usb4
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb5 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb6 -> ../../../devices/pci0000:00/0000:00:1d.0/usb6
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb7 -> ../../../devices/pci0000:00/0000:00:1d.1/usb7
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb8 -> ../../../devices/pci0000:00/0000:00:1d.2/usb8

radios toggled on:

lrwxrwxrwx 1 root root 0 Dec 19 22:32 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.7/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 2-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.7/usb2/2-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 3-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-0:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.1 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.1:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1/3-1.1:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.2 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.2:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.3 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.3:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.3:1.1 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.1
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.3:1.2 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.2
lrwxrwxrwx 1 root root 0 Dec 21 22:14 3-1.3:1.3 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.3
lrwxrwxrwx 1 root root 0 Dec 19 22:32 4-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.1/usb4/4-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 5-0:1.0 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-0:1.0
lrwxrwxrwx 1 root root 0 Dec 21 21:24 5-1 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-1
lrwxrwxrwx 1 root root 0 Dec 21 21:24 5-1:0.0 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:0.0
lrwxrwxrwx 1 root root 0 Dec 21 21:24 5-1:0.1 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:0.1
lrwxrwxrwx 1 root root 0 Dec 19 22:32 6-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.0/usb6/6-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 7-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.1/usb7/7-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 8-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.2/usb8/8-0:1.0
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb1 -> ../../../devices/pci0000:00/0000:00:1a.7/usb1
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb2 -> ../../../devices/pci0000:00/0000:00:1d.7/usb2
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb3 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb4 -> ../../../devices/pci0000:00/0000:00:1a.1/usb4
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb5 -> ../../../devices/pci0000:00/0000:00:1a.2/usb5
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb6 -> ../../../devices/pci0000:00/0000:00:1d.0/usb6
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb7 -> ../../../devices/pci0000:00/0000:00:1d.1/usb7
lrwxrwxrwx 1 root root 0 Dec 19 22:32 usb8 -> ../../../devices/pci0000:00/0000:00:1d.2/usb8

The difference in output is shown here:

lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.1 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.1:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1/3-1.1:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.2 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.2:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2/3-1.2:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.3 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.3:1.0 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.0
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.3:1.1 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.1
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.3:1.2 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.2
lrwxrwxrwx 1 root root 0 Dec 21 22:21 3-1.3:1.3 -> ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.3/3-1.3:1.3

What is going on here?  I'm stumped about how to fix this.  I don't know what to attack!  Is it this new usb device that I see with the radios?  Are the radios erroneously being treated as usb devices by udevd?  Any help is appreciated.

Thanks,

jdoggsc

Offline

#2 2017-12-28 08:51:42

tomaszc
Member
Registered: 2010-09-11
Posts: 19

Re: systemd-udevd using all CPU. Suspected errors caused by usb port

The ten same problem is on the Dell Vostro 3300
It looks like a regression bug in the kernel 4.14, appeared after the kernel update from 4.13 to 4.14

My lsusb:

Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 0c45:6450 Microdia 
Bus 001 Device 006: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics]
Bus 001 Device 005: ID 413c:8161 Dell Computer Corp. Integrated Keyboard
Bus 001 Device 003: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Probably the same error is described here:

https://forum.manjaro.org/t/high-cpu-us … iver/35972
https://dev.solus-project.com/T5224

Offline

#3 2017-12-28 14:02:28

jdoggsc
Member
Registered: 2011-08-15
Posts: 90

Re: systemd-udevd using all CPU. Suspected errors caused by usb port

Thanks for the response.  It's good that know i'm not the only one with the problem because it debunks my theory about some new hardware problem with my laptop.  I'd had the problem for weeks and  didn't get a response for several days and grew impatient.  I was spending as much time troubleshooting as I would have spent just wiping and reinstalling, so I did that.   It's not a solution, but I don't have the problem anymore.  I don't remember which version of the 4.14 kernel I had, but I have 4.14.8 right now and there's no problem with systemd-udevd and high CPU usage. 

So unless something was fixed between 4.14.7 and 4.14.8, (and 4.14.8 was released while I did the wipe and reinstall) I don't know what the problem could have been that's not affecting me now as well...

Offline

#4 2018-01-03 22:10:07

TAAPAye
Member
Registered: 2017-08-06
Posts: 11

Re: systemd-udevd using all CPU. Suspected errors caused by usb port

I am experiencing the same problem, and I'm surprised a system wipe has fixed it. My system is up to date (kernel 4.14.10-1). I'm on a Dell Studio 1558.

The only "solutions" I have found were to remove the "bluez-hid2hci" package or to roll back the kernel.

I tried reinstalling all Bluetooth related modules and udev to no avail which I woulda have expected to have a similar affect to reinstalling the entire OS.

Does Bluetooth work for you/ do you have the "bluez-hid2hci" package installed>

Offline

#5 2018-01-04 03:49:09

jdoggsc
Member
Registered: 2011-08-15
Posts: 90

Re: systemd-udevd using all CPU. Suspected errors caused by usb port

Well I didn't expect a reinstall to fix it, but hoped it would help isolate the problem.  It cleared away a lot of cruft and narrowed down possibilities.   Truth be told, I hadn't used bluetooth since I reinstalled. That's why it appeared to be fixed.  I installed bluez-utils today and couldn't find any bluetooth adapters in bluetoothctl.  the wiki directed me to install bluez-hid2hci (you did as well) to solve this problem for dell laptops.  Upon reboot, with btusb no longer blacklisted, bluetooth.service enabled in systemd, and bluez-hid2hci installed,the problem has reappeared. 

With bluez-hid2hci installed, bluetoothctl can now see my bluetooth adapter, but the CPU is pegged at 100% again.  So the system wipe certainly didn't fix the issue.
Uninstalling bluez-hid2hci appears to solve the CPU usage issue, but I lose bluetooth functionality, so it's not really a solution.

In the process of writing this response, I confirmed that downgrading to kernel 4.13.9 does allow bluetooth functionality without the high CPU usage by udev.  This is the solution I will be going with for the time being.

# pacman -U https://archive.archlinux.org/packages/l/linux/linux-4.13.9-1-x86_64.pkg.tar.xz https://archive.archlinux.org/packages/l/linux-headers/linux-headers-4.13.9-1-x86_64.pkg.tar.xz

I added linux, linux-headers, and my nvidia driver package to the Ignorepkg line in /etc/pacman.conf. It looks like I'll be checking back on this periodically to find when i can allow kernel upgrades again.  I hope this helps you.

Offline

#6 2018-01-14 11:27:28

pierro78
Member
Registered: 2013-05-18
Posts: 8

Re: systemd-udevd using all CPU. Suspected errors caused by usb port

same issue (same resolution : remove bluez-hid2hci) on dell precision m6500 here ... thanks for the tip !

Offline

#7 2018-01-20 01:53:53

jdoggsc
Member
Registered: 2011-08-15
Posts: 90

Re: systemd-udevd using all CPU. Suspected errors caused by usb port

I'm glad that someone other than me has benefitted from this thread.  I'm glad it helped.

Offline

Board footer

Powered by FluxBB