Re: kworker/0:3+pm hogging CPU

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

 



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



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

  Powered by Linux