Messages in this thread | | | Date | Tue, 1 Sep 2020 17:27:28 +0200 | From | Michal Hocko <> | Subject | Re: kworker/0:3+pm hogging CPU |
| |
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 -- Michal Hocko SUSE Labs
| |