[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFv23Qmc82p3o=1vDvmX5jkfbcOzoQFX7grxrKGwf1KD_vebig@mail.gmail.com>
Date: Wed, 25 Dec 2019 11:15:08 +0800
From: AceLan Kao <acelan.kao@...onical.com>
To: Alan Stern <stern@...land.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Kai-Heng Feng <kai.heng.feng@...onical.com>,
Thinh Nguyen <Thinh.Nguyen@...opsys.com>,
Harry Pan <harry.pan@...el.com>,
David Heinzelmann <heinzelmann.david@...il.com>,
Andrey Konovalov <andreyknvl@...gle.com>,
Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
Mathieu Malaterre <malat@...ian.org>,
linux-usb@...r.kernel.org,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] usb: hub: move resume delay at the head of all USB access functions
Here[1] are the dmesg and the usbmon log from wireshark, and
/sys/kernel/debug/usb/usbmon/0u.
I verified this issue on Dell XPS 13 + Dell Salomon WD19 docking
station(plug-in 3 USB disk on it)
After s2idle 7 times, 2 usb disks lost. But from wireshark log, the
packets look normal, no error.
So, I re-do the test again and log the usbmon/0u output, but it's greek to me.
Hope you can help to find some clues in the logs.
Thanks.
1. https://people.canonical.com/~acelan/bugs/usb_issue/
Alan Stern <stern@...land.harvard.edu> 於 2019年12月24日 週二 下午11:23寫道:
>
> 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
>
View attachment "dmesg_usb.log" of type "text/x-log" (122189 bytes)
Powered by blists - more mailing lists