Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Hardware] udevd stuck in 100% CPU loop removing and adding BT and Wifi

Need help with peripherals or devices?
Post Reply
Message
Author
HuV43
Posts: 3
Joined: 2022-12-08 16:27
Has thanked: 1 time
Been thanked: 1 time

[Hardware] udevd stuck in 100% CPU loop removing and adding BT and Wifi [SOLVED]

#1 Post by HuV43 »

Hello Debian users!

I set up a new server with Debian Bullseye and kernel 5.10.0-18-amd64. I got a new Ryzen 7000 CPU with a Gigabyte B650M AORUS ELITE AX motherboard. Well, it might be too new because there were install messages that the Debian firmware repository does not include drivers for the on board bluetooth and Wifi. No problem, I thought because this is a headless server.

First I noticed this repeating output from journalctl -f

Code: Select all

-- Journal begins at Mon 2022-12-05 12:27:34 MST. --
Dec 08 09:18:59 palmer systemd[51186]: Reached target Bluetooth.
Dec 08 09:19:01 palmer systemd[51186]: Stopped target Bluetooth.
Dec 08 09:19:04 palmer systemd[51186]: Reached target Bluetooth.
Dec 08 09:19:07 palmer systemd[51186]: Stopped target Bluetooth.
Dec 08 09:19:10 palmer systemd[51186]: Reached target Bluetooth.
Dec 08 09:19:12 palmer systemd[51186]: Stopped target Bluetooth.
Then I noticed udevd had spawned many procs and was pegging a CPU core to 100%.

Running udevadm monitor:

Code: Select all

KERNEL[53244.320134] bind     /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0 (usb)
KERNEL[53244.320149] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.1 (usb)
KERNEL[53244.320165] bind     /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.1 (usb)
KERNEL[53244.320183] bind     /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6 (usb)
UDEV  [53244.320394] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0 (usb)
UDEV  [53244.320437] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.1 (usb)
UDEV  [53244.408660] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0/bluetooth/hci0 (bluetooth)
KERNEL[53244.482573] remove   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0/bluetooth/hci0/rfkill56545 (rfkill)
KERNEL[53244.482603] remove   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0/bluetooth/hci0 (bluetooth)
KERNEL[53244.482612] unbind   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.1 (usb)
KERNEL[53244.482625] unbind   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0 (usb)
KERNEL[53244.482640] remove   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0 (usb)
KERNEL[53244.482654] remove   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.1 (usb)
KERNEL[53244.495819] unbind   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6 (usb)
KERNEL[53244.495856] remove   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6 (usb)
udevadm monitorUDEV  [53244.690033] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0/bluetooth/hci0/rfkill18753 (rfkill)
KERNEL[53245.238118] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6 (usb)
KERNEL[53245.260141] change   /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6 (usb)
KERNEL[53245.260183] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0 (usb)
KERNEL[53245.260196] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0/bluetooth/hci0 (bluetooth)
KERNEL[53245.260208] add      /devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0/bluetooth/hci0/rfkill56546 (rfkill)
It is constantly adding and removing the BT and wifi.

Finally running $ sudo /lib/systemd/systemd-udevd -D shows

Code: Select all

1-6: Device (SEQNUM=966857, ACTION=bind) ready for processing
1-6: sd-device-monitor: Passed 329 byte to netlink monitor
1-6: Processing device (SEQNUM=966857, ACTION=bind)
1-6: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id'
1-6: /usr/lib/udev/rules.d/60-libgphoto2-6.rules:9 Importing properties from results of builtin command 'usb_id'
1-6: Handling device node '/dev/bus/usb/001/094', devnum=c189:93
1-6: Preserve already existing symlink '/dev/char/189:93' to '../bus/usb/001/094'
1-6: sd-device: Created db file '/run/udev/data/c189:93' for '/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6'
1-6: Device (SEQNUM=966857, ACTION=bind) processed
1-6: sd-device-monitor: Passed 575 byte to netlink monitor
rfkill56634: Device (SEQNUM=966858, ACTION=remove) is queued
rfkill56634: Device (SEQNUM=966858, ACTION=remove) ready for processing
rfkill56634: sd-device-monitor: Passed 292 byte to netlink monitor
hci0: Device (SEQNUM=966859, ACTION=remove) is queued
hci0: SEQNUM=966859 blocked by SEQNUM=966858
1-6:1.1: Device (SEQNUM=966860, ACTION=unbind) is queued
1-6:1.1: Device (SEQNUM=966860, ACTION=unbind) ready for processing
1-6:1.1: sd-device-monitor: Passed 279 byte to netlink monitor
1-6:1.0: Device (SEQNUM=966861, ACTION=unbind) is queued
1-6:1.0: SEQNUM=966861 blocked by SEQNUM=966858
rfkill56634: Processing device (SEQNUM=966858, ACTION=remove)
1-6:1.0: Device (SEQNUM=966862, ACTION=remove) is queued
1-6:1.0: SEQNUM=966862 blocked by SEQNUM=966858
1-6:1.1: Device (SEQNUM=966863, ACTION=remove) is queued
1-6:1.1: SEQNUM=966863 blocked by SEQNUM=966860
1-6:1.1: Processing device (SEQNUM=966860, ACTION=unbind)
1-6:1.1: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id'
rfkill56634: Device (SEQNUM=966858, ACTION=remove) processed
rfkill56634: sd-device-monitor: Passed 387 byte to netlink monitor
hci0: Device (SEQNUM=966859, ACTION=remove) ready for processing
hci0: sd-device-monitor: Passed 242 byte to netlink monitor
1-6:1.0: SEQNUM=966861 blocked by SEQNUM=966859
1-6:1.0: SEQNUM=966862 blocked by SEQNUM=966859
hci0: Processing device (SEQNUM=966859, ACTION=remove)
1-6:1.1: sd-device: Created db file '/run/udev/data/+usb:1-6:1.1' for '/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.1'
1-6:1.1: Device (SEQNUM=966860, ACTION=unbind) processed
1-6:1.1: sd-device-monitor: Passed 357 byte to netlink monitor
1-6:1.1: Device (SEQNUM=966863, ACTION=remove) ready for processing
1-6:1.1: sd-device-monitor: Passed 338 byte to netlink monitor
1-6:1.1: Processing device (SEQNUM=966863, ACTION=remove)
hci0: Device (SEQNUM=966859, ACTION=remove) processed
1-6:1.1: Device (SEQNUM=966863, ACTION=remove) processed
1-6:1.1: sd-device-monitor: Passed 416 byte to netlink monitor
hci0: sd-device-monitor: Passed 399 byte to netlink monitor
1-6:1.0: Device (SEQNUM=966861, ACTION=unbind) ready for processing
1-6:1.0: sd-device-monitor: Passed 279 byte to netlink monitor
1-6:1.0: SEQNUM=966862 blocked by SEQNUM=966861
1-6:1.0: Processing device (SEQNUM=966861, ACTION=unbind)
1-6:1.0: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id'
1-6:1.0: sd-device: Created db file '/run/udev/data/+usb:1-6:1.0' for '/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:0c.0/0000:0e:00.0/usb1/1-6/1-6:1.0'
1-6:1.0: Device (SEQNUM=966861, ACTION=unbind) processed
1-6:1.0: sd-device-monitor: Passed 357 byte to netlink monitor
1-6:1.0: Device (SEQNUM=966862, ACTION=remove) ready for processing
1-6:1.0: sd-device-monitor: Passed 338 byte to netlink monitor
1-6:1.0: Processing device (SEQNUM=966862, ACTION=remove)
1-6:1.0: Device (SEQNUM=966862, ACTION=remove) processed
1-6:1.0: sd-device-monitor: Passed 416 byte to netlink monitor
I am confused because I masked bluetooth.target and stopped and disabled bluetooth.service. Systemctl status shows these are dead.

Any ideas what commands I can run to get more info or stop the CPU madness?

Update: I installed the backport firmware-linux and firmware-linux-nonfree pakages, rebooted, and it did not fix the issue.

Update2: dmesg output is this repeating with the device number incremented each time:

Code: Select all

[  538.620848] usb 1-6: new full-speed USB device number 71 using xhci_hcd
[  539.023178] usb 1-6: New USB device found, idVendor=8087, idProduct=0032, bcdDevice= 0.00
[  539.023181] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  539.051012] Bluetooth: hci0: Reading Intel version information failed (-22)
[  539.051018] Bluetooth: hci0: Intel Read version failed (-22)
[  539.051061] Bluetooth: hci0: Intel reset sent to retry FW download
[  539.055230] usb 1-6: USB disconnect, device number 71
[  539.057077] xhci_hcd 0000:0e:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[  539.564805] usb 1-6: new full-speed USB device number 72 using xhci_hcd
[  539.967208] usb 1-6: New USB device found, idVendor=8087, idProduct=0032, bcdDevice= 0.00
[  539.967210] usb 1-6: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[  539.995013] Bluetooth: hci0: Reading Intel version information failed (-22)
[  539.995022] Bluetooth: hci0: Intel Read version failed (-22)
[  539.995102] Bluetooth: hci0: Intel reset sent to retry FW download
Update3:
Trying to remove wireless modules from the kernel. I recognized btusb from an error log and got this output with lsmod | grep bt:

Code: Select all

btusb                  65536  0
btrtl                  28672  1 btusb
btbcm                  20480  1 btusb
btintel                32768  1 btusb
bluetooth             749568  4 btrtl,btintel,btbcm,btusb
usbcore               331776  4 xhci_hcd,usbhid,btusb,xhci_pci
I wouldn't mind removing all of these, even if it disables usb ports. I tried rmmod and modprobe -r but it doesn't seem to work. If I run on btusb, there is no output. If I run on any of the others, I get:

Code: Select all

rmmod: ERROR: Module bluetooth is in use by: btrtl btintel btbcm btusb
Next, I made blacklist.conf in /etc/modprobe.d and added each module name on its own line and rebooted. lsmod shows they are all still loaded!

Update4: Solved! I had not included the blacklist keyword in blacklist.conf in /etc/modprobe.d. Thanks for suggesting blacklist!
Last edited by HuV43 on 2022-12-08 23:41, edited 3 times in total.

CwF
Global Moderator
Global Moderator
Posts: 2638
Joined: 2018-06-20 15:16
Location: Colorado
Has thanked: 41 times
Been thanked: 192 times

Re: [Hardware] udevd stuck in 100% CPU loop removing and adding BT and Wifi

#2 Post by CwF »

Why would you not turn it off in the bios if you're not going to use it?

User avatar
canci
Global Moderator
Global Moderator
Posts: 2502
Joined: 2006-09-24 11:28
Has thanked: 136 times
Been thanked: 136 times

Re: [Hardware] udevd stuck in 100% CPU loop removing and adding BT and Wifi

#3 Post by canci »

Or if it can't be done in the bios, then just blacklist the modules. The system is probably busy with handling either buggy drivers or maybe also a hardware failure.
Image Stable / Asus VivoBook X421DA / AMD Ryzen 7 3700U / Radeon Vega Mobile Gfx (Picasso) / 8 GB RAM / 512GB NVMe

READ THIS:

* How to Post a Thread Here
* Other Tips and Great Resources

HuV43
Posts: 3
Joined: 2022-12-08 16:27
Has thanked: 1 time
Been thanked: 1 time

Re: [Hardware] udevd stuck in 100% CPU loop removing and adding BT and Wifi

#4 Post by HuV43 »

CwF wrote: 2022-12-08 21:10 Why would you not turn it off in the bios if you're not going to use it?
I updated to latest bios and looked in all the menus but did not see an option to disable wireless. That was the first thing I tried!

HuV43
Posts: 3
Joined: 2022-12-08 16:27
Has thanked: 1 time
Been thanked: 1 time

Re: [Hardware] udevd stuck in 100% CPU loop removing and adding BT and Wifi

#5 Post by HuV43 »

canci wrote: 2022-12-08 21:45 just blacklist the modules
It worked. Thank you!

Post Reply