Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 20 Jul 2020 19:45:30 +0200
From:   Michal Hocko <mhocko@kernel.org>
To:     Alan Stern <stern@rowland.harvard.edu>
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
Message-ID: <20200720174530.GB4061@dhcp22.suse.cz>
References: <20200720083956.GA4074@dhcp22.suse.cz>
 <20200720135857.GB1228057@rowland.harvard.edu>
 <20200720143213.GJ4074@dhcp22.suse.cz>
 <20200720151255.GE1228057@rowland.harvard.edu>
 <20200720163355.GA4061@dhcp22.suse.cz>
 <20200720173807.GJ1228057@rowland.harvard.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200720173807.GJ1228057@rowland.harvard.edu>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon 20-07-20 13:38:07, Alan Stern wrote:
> On Mon, Jul 20, 2020 at 06:33:55PM +0200, Michal Hocko wrote:
> > On Mon 20-07-20 11:12:55, Alan Stern wrote:
> > [...]
> > > 	sudo echo 'module usbcore =p' >/debug/dynamic_debug/control
> > > 
> > > Then wait long enough for some interesting messages to appear in the 
> > > kernel log (it should only take a few seconds if the worker thread is as 
> > > busy as you say) and collect the output from the dmesg command.
> > > 
> > > To turn dynamic debugging back off when you're finished, use the same 
> > > command with "=p" changed to "-p".
> > 
> > [   95.395815] hub 2-0:1.0: state 7 ports 6 chg 0006 evt 0000
> > [   95.395824] usb usb2-port1: status 0088, change 0000, 5.0 Gb/s
> > [   95.395838] usb usb2-port2: status 0088, change 0000, 5.0 Gb/s
> > [   95.396016] hub 2-0:1.0: hub_suspend
> > [   95.396023] usb usb2: bus auto-suspend, wakeup 1
> > [   95.396029] usb usb2: bus suspend fail, err -16
> 
> Okay, that's the problem.  You may get more specific information about 
> the suspend failure if you turn on dynamic debugging for the xhci-hcd 
> module (same command as above but with xhci-hcd instead of usbcore).

Would that help to pinpoint the problem down?

> If you want a quick way to prevent this from happening, you can do:
> 
> 	sudo echo on >/sys/bus/usb/devices/usb2/power/control
> 
> That won't actually fix anything, but it will stop the system from 
> automatically trying to suspend usb2 root hub.

Yes, that helped to put some relief to the machine. 

-- 
Michal Hocko
SUSE Labs