From: Oliver Neukum <oneukum@suse.com>
To: "Schmid, Carsten" <Carsten_Schmid@mentor.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: AW: Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters
Date: Wed, 14 Aug 2019 15:07:53 +0200 [thread overview]
Message-ID: <1565788073.25764.8.camel@suse.com> (raw)
In-Reply-To: <f5e22fea4e1c4baeb2fc98d324ad9060@SVR-IES-MBX-03.mgc.mentorg.com>
Am Mittwoch, den 14.08.2019, 08:56 +0000 schrieb Schmid, Carsten :
> > This is on a lower layer than ax88179. This comes from xhci_hcd.
> > Is this a regression?
> >
>
> I don't think its a regression.
It would be better to know than to assume.
> Is there something i can do to force an error message to be seen
> when the ETH2USB adapter stalls?
You can activate dynamic debugging for the xhci_hcd module
Remember that no data to transfer is not an error as such.
> My current assumption is that the signal quality of the USB port is at a
> corner case, and therefore some "better" Adapters work, some "bad ones"
> don't. But as there is no error message seen in the dmesg, i am somehow lost.
Two things you can do:
1. Generate a usbmon trace (it will be gigantic though)
2. Activate dynamic debugging for the xhci_hcd module
Regards
Oliver
next prev parent reply other threads:[~2019-08-14 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 8:17 Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters Schmid, Carsten
2019-08-14 8:31 ` Oliver Neukum
2019-08-14 8:56 ` AW: " Schmid, Carsten
2019-08-14 10:22 ` Schmid, Carsten
2019-08-14 13:07 ` Oliver Neukum [this message]
2019-08-15 12:02 ` AW: " Schmid, Carsten
2019-08-16 11:56 ` Schmid, Carsten
2019-08-19 12:11 ` Oliver Neukum
2019-08-19 12:27 ` AW: " Schmid, Carsten
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=1565788073.25764.8.camel@suse.com \
--to=oneukum@suse.com \
--cc=Carsten_Schmid@mentor.com \
--cc=f.fainelli@gmail.com \
--cc=linux-usb@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 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).