From: Greg KH <greg@kroah.com>
To: Eric Blau <eblau@eblau.com>
Cc: stable@vger.kernel.org
Subject: Re: [regression] USB power management failure to suspend / high CPU usage
Date: Thu, 3 Jan 2019 10:32:26 +0100 [thread overview]
Message-ID: <20190103093226.GA13375@kroah.com> (raw)
In-Reply-To: <CADU241MmYH+BxVZcgtcHj+wW1gPTtBbowJTxBRgj3U_mG-oGQQ@mail.gmail.com>
On Wed, Jan 02, 2019 at 10:42:55AM -0500, Eric Blau wrote:
> On Sun, Dec 23, 2018 at 11:28 AM Greg KH <greg@kroah.com> wrote:
> >
> > On Sun, Dec 23, 2018 at 08:49:42AM -0500, Eric Blau wrote:
> > >
> > > The behavior exists in 4.19.8 and 4.19.11, the kernel versions I have
> > > upgraded to with Arch Linux, so the regression was introduced sometime
> > > between 4.19.4 and 4.19.8. Hibernate still works but when I resume
> > > from hibernate, there is a ksoftirqd and kworker thread/process
> > > together taking up 100% of one core. If I turn off auto power control
> > > for usb1 and usb2, the threads stop spinning. i.e.,
> > >
> > > echo 'on' > '/sys/bus/usb/devices/usb1/power/control
> > >
> > > Any suggestions as to where this regression was introduced and what
> > > can be done to fix it?
> >
> > Sorry, this is a known issue, will be fixed in the next 4.19 release
> > that should be out next week.
> >
> > If you are curious, it is fixed by commit 45f750c16cae ("xhci: Don't
> > prevent USB2 bus suspend in state check intended for USB3 only") in
> > Linus's tree.
>
> Hi Greg,
>
> I've upgraded to 4.20 and the same regression still exists. I know
> this is not a stable release currently, but 4.20 has 45f750c16cae
> merged as commit 93a86395b429:
>
> commit 93a86395b429c3a68a0d029f584f39890c0801b2
> Merge: 45f750c16cae 28a86092b175
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> AuthorDate: Fri Dec 14 17:06:09 2018 +0100
> Commit: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> CommitDate: Fri Dec 14 17:06:09 2018 +0100
>
> Merge tag 'usb-serial-4.20-rc7' of
> https://git.kernel.org/pub/scm/linux/kernel/git/johan/usb-serial into
> usb-linus
>
>
> The same workaround is still effective, but I thought I'd let you know
> that I'm still experiencing the same issue. If there's anything else I
> can do to help track this down, please let me know.
Can you post the information that you are still having this issue on the
linux-usb@vger.kernel.org mailing list, along with any kernel logs that
you might have that shows this? The developers there can help you out.
thanks,
greg k-h
next prev parent reply other threads:[~2019-01-03 9:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADU241PERmgQQ4jEW4k_eUCveptLCojptQMVnpLcv_DQS3N-tg@mail.gmail.com>
2018-12-23 16:28 ` [regression] USB power management failure to suspend / high CPU usage Greg KH
2018-12-23 19:23 ` Eric Blau
2019-01-02 15:42 ` Eric Blau
2019-01-03 9:32 ` Greg KH [this message]
2019-02-14 14:57 Mathias Nyman
-- strict thread matches above, loose matches on Subject: below --
2019-02-20 17:28 Mathias Nyman
2019-02-22 1:05 Eric Blau
2019-02-25 22:11 Ivan Mironov
2019-03-04 15:15 Mathias Nyman
2019-03-04 15:53 Eric Blau
2019-03-21 13:32 Eric Blau
2019-03-21 14:54 Mathias Nyman
2019-03-21 15:40 Eric Blau
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=20190103093226.GA13375@kroah.com \
--to=greg@kroah.com \
--cc=eblau@eblau.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.