linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Michal Hocko <mhocko@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-usb@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: kworker/0:3+pm hogging CPU
Date: Tue, 21 Jul 2020 12:14:44 -0400	[thread overview]
Message-ID: <20200721161444.GE1272082@rowland.harvard.edu> (raw)
In-Reply-To: <20200721160025.GP4061@dhcp22.suse.cz>

On Tue, Jul 21, 2020 at 06:00:25PM +0200, Michal Hocko wrote:
> On Tue 21-07-20 10:33:25, Alan Stern wrote:
> [...]
> 
> Thanks a lot for your analysis. The laptop is slowly dying so this can
> be related.
> 
> > So yes, this looks like a hardware design error.  Turning off 
> > autosuspend by writing to the sysfs power/control file is probably the 
> > best way to handle the problem.
> 
> I can use that workaround. But it seems that this also prevents me from
> suspending the maching into RAM with
> PM: Some devices failed to suspend, or early wake event detected
> 
> :/
> 
> If there is any workaround for that then I would be really happy but
> considering the overal state of the machine I suspect this is not the
> case.

As far as I know there is no workaround.

Of course, you could build your own personal kernel with the 
over-current test removed from the driver.  But keeping that up-to-date 
would be a nuisance.

> Thanks again for your great help!

You're welcome.

Alan Stern

  reply	other threads:[~2020-07-21 16:14 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 [this message]
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
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=20200721161444.GE1272082@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).