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: Mon, 20 Jul 2020 11:12:55 -0400 [thread overview]
Message-ID: <20200720151255.GE1228057@rowland.harvard.edu> (raw)
In-Reply-To: <20200720143213.GJ4074@dhcp22.suse.cz>
On Mon, Jul 20, 2020 at 04:32:13PM +0200, Michal Hocko wrote:
> On Mon 20-07-20 09:58:57, Alan Stern wrote:
> [...]
> > Can you provide the contents of /sys/kernel/debug/usb/devices and also a
>
> attached.
It looks like you've got just two devices, only one of which is in use,
on bus 1 (the non-SuperSpeed bus) and nothing on bus 2.
> > usbmon trace showing a few rounds of this recurring activity?
>
> This is not my area so I will need some help here. I assume I should
> look for debug/usb/usbmon which contains quite some files for me
> 0s 0u 1s 1t 1u 2s 2t 2u
> most of them provide data when cating them.
The interesting files are 1u (for bus 1) and 2u (for bus 2). At the
moment, though, we don't know which bus the troublesome
device/controller is on.
> > section of the dmesg log with dynamic debugging enabled for the usbcore
> > module, as well.
>
> Could you give me more details steps please?
Do:
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".
Alan Stern
next prev parent reply other threads:[~2020-07-20 15:12 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 [this message]
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
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=20200720151255.GE1228057@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).