How to Fix ‘Systemd-udevd High CPU Usage’ in Ubuntu

Noticing your Ubuntu laptop or server fans running at maximum velocity, system responsiveness grinding to a crawl, and terminal resource monitors like top or htop displaying systemd-udevd consuming 100% CPU on multiple cores indicates a serious hardware event storm. In Linux systems, systemd-udevd is the system daemon responsible for managing dynamic device nodes in /dev, handling kernel hardware events (uevents), and executing rules defined in /etc/udev/rules.d/. When a malfunctioning peripheral, damaged USB connector, or broken driver script causes the kernel to flood the udev daemon with thousands of connect/disconnect interrupts per second, systemd-udevd enters an infinite processing loop. This troubleshooting guide shows you how to trace hardware uevents, isolate faulty devices, and resolve high CPU utilisation in Ubuntu.

Why Does systemd-udevd Consume Excessive CPU?

The udev daemon is designed to run asynchronously with near-zero overhead. When it consumes excessive processor time, the underlying cause is almost always an external event flood:

  • Hardware Interrupt Storms (Uevent Loops): Defective USB flash drives, failing SD card readers, or broken Wi-Fi controllers rapidly alternating between power states, generating continuous uevents.
  • Corrupted or Broken Custom Udev Rules: Scripted udev rules in /etc/udev/rules.d/ that run blocking external commands or trigger actions that themselves generate new uevents, creating an infinite loop.
  • ACPI / GPE Interrupt Loops: Faulty laptop motherboard firmware triggering constant General Purpose Event (GPE) interrupts in the ACPI subsystem.
  • Failing Storage Drive Cables: Loose SATA cables or failing NVMe bridges resetting their PCIe bus connections repeatedly.

Method 1: Monitor Live Hardware Events Using udevadm

The udevadm monitor tool listens directly to kernel uevents and udev processing events, instantly revealing which hardware device is flooding the system.

  1. Open your terminal by pressing Ctrl + Alt + T.
  2. Execute the real-time event monitoring tool with root privileges:
    sudo udevadm monitor --property
  3. Observe the terminal stream. Under healthy conditions, the output is completely static unless you plug in a new device.
  4. If the screen rapidly scrolls with endless messages, inspect the DEVPATH and SUBSYSTEM fields (for example, pointing to usb, pci, or block).
  5. Identify the device node generating the flood (e.g. /dev/sdb, wlan0, or a specific USB bus ID).

Method 2: Disconnect Suspect USB and PCIe Peripherals

Once you identify the offending subsystem from udevadm, unplugging the physical accessory immediately relieves the daemon.

  1. Disconnect all external USB devices: flash drives, external webcams, audio interfaces, and docks.
  2. If your laptop has an integrated SD card reader, check if a damaged card is inserted.
  3. Monitor your CPU usage with top. If CPU usage drops from 100% back to 0.1%, the disconnected device or its physical port is electrically damaged.

Method 3: Inspect and Clean Custom Udev Rules

Third-party software (such as Android ADB tools, virtual machines, or crypto hardware wallets) frequently install custom udev rules that can conflict with modern systemd versions.

  1. Navigate to the custom udev configuration directory:
    cd /etc/udev/rules.d/ && ls -la
  2. Temporarily move custom rules to a backup directory to test if CPU usage normalises:
    sudo mkdir -p /tmp/udev_backup && sudo mv *.rules /tmp/udev_backup/
  3. Reload the udev daemon rules and trigger updated configuration:
    sudo udevadm control --reload && sudo udevadm trigger
  4. Check top. If CPU utilisation normalises, inspect the backed-up rule files individually to find the rule running recursive scripts.

Method 4: Check for ACPI GPE Interrupt Storms

If the hardware event storm originates from ACPI motherboard pins, identifying and masking the high-frequency GPE restores normal clock cycles.

  1. Inspect ACPI interrupt counts:
    grep -r . /sys/firmware/acpi/interrupts/ | grep -v ' 0'
  2. Look for a specific GPE interrupt (e.g. gpe6F) showing millions of recorded hits.
  3. Temporarily disable the runaway interrupt pin:
    sudo sh -c 'echo "disable" > /sys/firmware/acpi/interrupts/gpeXX'
    (Replace XX with the specific hexadecimal GPE number identified in the previous step).
  4. Verify that systemd-udevd CPU usage drops to normal levels immediately.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.