From: Michal Hocko <mhocko@suse.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Salvatore Bonaccorso <carnil@debian.org>,
LKML <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Dirk Kostrewa <dirk.kostrewa@mailbox.org>
Subject: Re: kworker/0:3+pm hogging CPU
Date: Tue, 1 Sep 2020 17:27:28 +0200 [thread overview]
Message-ID: <20200901152728.GI16650@dhcp22.suse.cz> (raw)
In-Reply-To: <38dfdef4-f9ab-1755-8418-2285d843af86@linux.intel.com>
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
next prev parent reply other threads:[~2020-09-01 16:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 8:39 kworker/0:3+pm hogging CPU Michal Hocko
2020-07-20 13:58 ` Alan Stern
2020-07-20 14:32 ` Michal Hocko
2020-07-20 15:12 ` Alan Stern
2020-07-20 16:33 ` Michal Hocko
2020-07-20 17:38 ` Alan Stern
2020-07-20 17:45 ` Michal Hocko
2020-07-20 17:48 ` Alan Stern
2020-07-20 18:16 ` Michal Hocko
2020-07-20 20:02 ` Alan Stern
2020-07-21 5:59 ` Michal Hocko
2020-07-21 14:33 ` Alan Stern
2020-07-21 16:00 ` Michal Hocko
2020-07-21 16:14 ` Alan Stern
2020-08-29 9:50 ` Salvatore Bonaccorso
2020-08-29 15:59 ` Alan Stern
2020-08-31 11:37 ` Mathias Nyman
2020-09-01 15:27 ` Michal Hocko [this message]
2020-09-04 15:57 ` Dirk Kostrewa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200901152728.GI16650@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=carnil@debian.org \
--cc=dirk.kostrewa@mailbox.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).