Linux-USB Archive on lore.kernel.org
 help / color / Atom feed
From: "Schmid, Carsten" <Carsten_Schmid@mentor.com>
To: Oliver Neukum <oneukum@suse.com>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: AW: Strange behaviour of D-Link DUB-1312 USB 3.0 Adapters
Date: Wed, 14 Aug 2019 10:22:51 +0000
Message-ID: <b3b7161ab7f34301aedfd5e5ba3d41a7@SVR-IES-MBX-03.mgc.mentorg.com> (raw)
In-Reply-To: <f5e22fea4e1c4baeb2fc98d324ad9060@SVR-IES-MBX-03.mgc.mentorg.com>

>>> 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.
>
I can see the same on a 4.14.102.

Next observation:
After some - long - time (> 15 minutes) a hanging ping
says:
ping: sendto: Network is unreachable

After this, without doing anything, i can start ping again
and it works:

$:~# ping 134.86.56.80
PING 134.86.56.80 (134.86.56.80): 56 data bytes
ping: sendto: Network is unreachable
$:~# ping 134.86.56.80
PING 134.86.56.80 (134.86.56.80): 56 data bytes
64 bytes from 134.86.56.80: seq=0 ttl=63 time=3.206 ms
64 bytes from 134.86.56.80: seq=1 ttl=63 time=0.662 ms

Looks like a higher rate of transfers causes a stall or retries
or whatever - but without any message i'm lost.
I can reproduce this 100%.

Someone there who has any advice what i can do to
track this down?

Best regards
Carsten

  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   ` AW: " Schmid, Carsten
2019-08-14 10:22     ` Schmid, Carsten [this message]
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 publically 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=b3b7161ab7f34301aedfd5e5ba3d41a7@SVR-IES-MBX-03.mgc.mentorg.com \
    --to=carsten_schmid@mentor.com \
    --cc=f.fainelli@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    /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

Linux-USB Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-usb/0 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/ https://lore.kernel.org/linux-usb \
		linux-usb@vger.kernel.org
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-usb


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git