@b9AcE
I just tested our latest vendor kernel package again, and now I do not have the udev-worker loop anymore: Upgrading to kernel version 6 from 5.10 - #19 by MichaIng
Can you verify that it has gone in your case as well, and there is no constant 5% CPU load anymore?
Yep. Everything seems fine.
Only seeing real processes in the like top 15 or something during about 2 minutes of staring at it, except for one kworker popping up once but it was listed as 0.0% CPU use still, so can be ignored.
I’ve been on this kernel since June 4 and it has been just fine.
There was an issue about me during the upgrade having to revert a bit of dtb-crust leftover from our adventure in order to have the upgrade complete, but I’m an irrelevant edge-case in that regard and besides I’ve forgotten the details of that.
Since then I have not seen any issues except one case of the very rare getting stuck during reboot apparently at kernel-exit. Everything else is apparently fine.
Thanks again!
Thanks for verifying. Kernel workers are normal, just that udev-worker that never disappeared, as if a device was detached and re-attached in a loop, was not normal and caused quite some load. IIRC, on each loop, all udev rules were reloaded (parsed and in case applied again), which was the major reason for the load.
I remember. On a quick review of the maintainer scripts, I could not find an issue, but I wanted to add a debug flag to all scripts to find the command and condition which leads to the faulty dtb-* directory removal.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.