Re: kworker/0:3+pm hogging CPU

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

meanwhile, I convinced Dell that I have a hardware issue (and not a Linux issue), and Dell has replaced the mainboard of my laptop. After that, both the USB over-current kernel messages and the kworker processes with permanent high CPU load are gone. So, this was indeed a hardware issue!

Many thanks for your feedback and help!

Best regards,

Dirk.

Am 01.09.20 um 17:27 schrieb Michal Hocko:

On Mon 31-08-20 14:37:10, Mathias Nyman wrote:
[...]
I can't come up with any good solution to this right now.
Only bad ideas such as
a. Add a sleep to the over-current case,
    doesn't solve anything else than the ~100% cpu hogging part of the problem
This sounds like a better thing from the user space point of view. I do
not have any insight on what kind of other side effects this might have
so I didn't dare to try that on my piece of (broken) HW. I do not see
the problem all the time and I plan to replace it soon anyway.

Considering that tweaking the power management helps maybe that could be
done automagically after many consecutive failures.

Just my 2c



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux