Linux-USB Archive on
 help / color / Atom feed
From: "Schmid, Carsten" <>
To: Oliver Neukum <>,
	"" <>
Cc: "" <>
Subject: AW: Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters
Date: Wed, 14 Aug 2019 08:56:38 +0000
Message-ID: <> (raw)
In-Reply-To: <>

>> Plugging them into the same port (!) on my device one of them is
>> recognized as SuperSpeed, the other as high speed ???
>> (working on 4.14.129 LTS)
>> From dmesg, the "faulty" one:
>> [  530.585871] usb 1-2: new high-speed USB device number 4 using
>> xhci_hcd   <<<<<<<<< HUH ????
> XHCI is not like EHCI. It needs no companion controller, as it serves
> all speeds.
> This is on a lower layer than ax88179. This comes from xhci_hcd.
> Is this a regression?
I don't think its a regression.

Meanwhile some more strange things:
Depending on how fast i plug in the "faulty" one, sometimes
it is recognized as a SuperSpeed too.
But then, i have made the following observation:
- ping from the device to a host works (and vice versa)
- scp-ing a file from host to to device the adapter suddenly stalls,
  but i don't see any error message in dmesg
- device then is stalled, ping doesn't work any more
- unbind/bind driver recovers the adapter
  (and always returns SuperSpeed mode)
- ping works, scp breaks it again
- leaving the device in stall, scp tells "lost connection"
  on the host after ~10 minutes

Is there something i can do to force an error message to be seen
when the ETH2USB adapter stalls?

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.

Best regards

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14  8:17 Schmid, Carsten
2019-08-14  8:31 ` Oliver Neukum
2019-08-14  8:56   ` Schmid, Carsten [this message]
2019-08-14 10:22     ` AW: " Schmid, Carsten
2019-08-14 13:07     ` Oliver Neukum
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-USB Archive on

Archives are clonable:
	git clone --mirror linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ \
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone