Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Udevd hogging cpu on startup.  (Read 788 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] Udevd hogging cpu on startup.

On startup udevd puts up a lot of load on cpu. The usage is 60-70% on both cores(while idle  they barely cross 1%). The core temps on laptops reach 80-90 celsius on my laptop(idle temps are 50-60 celcius). I can also hear the fan spinning, when idly I barely hear it at all.

I usually just kill udevd after jumping into X to solve this issue. This has been the case from the beginning when I started using Artix in 2019, I just never bothered to do anything about it. Does anyone know what's going on?

Re: Udevd hogging cpu on startup.

Reply #1 –
Also I have to restart udevd, every time I want to plugin a usb device

Re: Udevd hogging cpu on startup.

Reply #2 –
Quote from: sarmin – on
Also I have to restart udevd, every time I want to plugin a usb device


It's expected. Udevd is the program responsible for listening for device plugging and unplugging events and rebroadcasting them to the rest of the programs. Without udevd, programs have no way of knowing when devices are added or removed.

My guess is some malfunctioning portion of your computer is overloading udevd with "plug-unplug" events. With udevd running, check the output of the command udevadm monitor.

Re: Udevd hogging cpu on startup.

Reply #3 –
Udevd is supposed to kill all the extra processes/worker threads it spawns after a while at least.

Re: Udevd hogging cpu on startup.

Reply #4 –
Quote from: capezotte – on
It's expected. Udevd is the program responsible for listening for device plugging and unplugging events and rebroadcasting them to the rest of the programs. Without udevd, programs have no way of knowing when devices are added or removed.

My guess is some malfunctioning portion of your computer is overloading udevd with "plug-unplug" events. With udevd running, check the output of the command udevadm monitor.

That is correct. I ran udevadm monitor and the source of udev's overloading turned out to be a udev rule(to set brightness on boot) that I created a long while ago.  :-[  .Removed the rule and stuff works fine.

Thanks for the help mate!!