From: Alan Stern <stern@rowland.harvard.edu>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Harry Pan <harry.pan@intel.com>,
David Heinzelmann <heinzelmann.david@gmail.com>,
Andrey Konovalov <andreyknvl@google.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Mathieu Malaterre <malat@debian.org>, <linux-usb@vger.kernel.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: hub: move resume delay at the head of all USB access functions
Date: Tue, 24 Dec 2019 10:23:12 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1912241021580.28718-100000@netrider.rowland.org> (raw)
In-Reply-To: <CAFv23Qn9h=pwaHkiMB2ci-OaR54gY6fdc1Q_7ZMz5mH7wHr9+w@mail.gmail.com>
On Mon, 23 Dec 2019, AceLan Kao wrote:
> > > you'll encounter the below errors sometime.
> > > After the issue happens, have to re-plug the USB cable to recover.
> > >
> > > [ 837.483573] hub 2-3:1.0: hub_ext_port_status failed (err = -71)
> > > [ 837.490889] hub 2-3:1.0: hub_ext_port_status failed (err = -71)
> > > [ 837.506780] usb 2-3-port4: cannot disable (err = -71)
> >
> > You need to do a better job of figuring out why these errors occur. It
> > is not connected to the resume delay; there must be a different reason.
> > Hint: This is the sort of error you would expect to see if the kernel
> > tried to resume a device while its parent hub was still suspended.
> Once this error shows, the USB port doesn't work until re-plug the cable.
> I have no idea what else I can do to this, do you have any idea that I
> could try?
> Thanks.
Maybe you can collect a usbmon trace showing what happens when the
error occurs. There's probably something going on that you aren't
aware of.
Alan Stern
next prev parent reply other threads:[~2019-12-24 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 2:59 [PATCH] usb: hub: move resume delay at the head of all USB access functions AceLan Kao
2019-12-20 15:48 ` Alan Stern
2019-12-23 4:29 ` AceLan Kao
2019-12-24 15:23 ` Alan Stern [this message]
2019-12-25 3:15 ` AceLan Kao
2019-12-26 4:13 ` Pan, Harry
2019-12-26 9:07 ` AceLan Kao
2020-01-02 21:37 ` Alan Stern
2020-01-03 5:26 ` Kai-Heng Feng
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=Pine.LNX.4.44L0.1912241021580.28718-100000@netrider.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=Thinh.Nguyen@synopsys.com \
--cc=acelan.kao@canonical.com \
--cc=andreyknvl@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=harry.pan@intel.com \
--cc=heinzelmann.david@gmail.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=malat@debian.org \
--cc=nsaenzjulienne@suse.de \
/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).