Realtek 8153-based ethernet adapter on usb3 eventually stops working requiring unplug/replug

Bug #1586195 reported by Mike Gerow
78
This bug affects 14 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
High
Unassigned
Xenial
Expired
High
Unassigned

Bug Description

Continued in Bug #1622322.

Seems to be paired with dmesg entries like this on the trusty kernel:

[24763.731054] usb 4-4.2: Disable of device-initiated U1 failed.
[24763.734507] usb 4-4.2: Disable of device-initiated U2 failed.
[24763.734594] r815x 4-4.2:2.0 eth3: unregister 'r815x' usb-0000:00:14.0-4.2, RTL8153 ECM Device
[24763.802963] usb 4-4.2: Set SEL for device-initiated U1 failed.
[24763.806450] usb 4-4.2: Set SEL for device-initiated U2 failed.
[24763.809953] usb 4-4.2: usb_reset_and_verify_device Failed to disable LTM
[24763.809953] .
[24763.810579] usb 4-4.2: USB disconnect, device number 7
[24763.940765] userif-1: sent link down event.
[24763.940769] userif-1: sent link up event.

And like this on mainline:

[ 259.731142] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd
[ 259.752915] usb 4-3: New USB device found, idVendor=0bda, idProduct=8153
[ 259.752918] usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 259.752920] usb 4-3: Product: USB 10/100/1000 LAN
[ 259.752921] usb 4-3: Manufacturer: Realtek
[ 259.752922] usb 4-3: SerialNumber: 000001000000
[ 259.909368] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd
[ 259.993254] r8152 4-3:1.0 eth0: v1.08.3
[ 260.079151] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 296.266600] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 300.785814] r8152 4-3:1.0 eth0: Stop submitting intr, status -71
[ 302.832697] usb 4-3: usb_reset_and_verify_device Failed to disable LTM
[ 302.832697] .
[ 302.833086] usb 4-3: USB disconnect, device number 4

Mainline version fyi:
[ 0.000000] Linux version 4.6.0-040600-generic (kernel@gomeisa) (gcc version 5.3.1 20160509 (Ubuntu 5.3.1-19ubuntu1) ) #201605151930 SMP Sun May 15 23:32:59 UTC 2016

I also get a similar message about 'Failed to disable LTM' if I just unplug the device before the breakage occurs.

I've attached lsusb before the breakage occurs (so you can see the device) from the mainline kernel.

Interestingly it appears the drivers on trusty and wily/mainline are different (r815x vs r8152) yet still exhibit similar troubles. I'm still digging around to try and figure out why this doesn't seem to be working, but I was wondering if you all had any idea what might be going pear-shaped here.

Thanks!

Revision history for this message
Mike Gerow (gerow) wrote :
Revision history for this message
Mike Gerow (gerow) wrote :

Oh, and here's the full dmesg output from the 4.6 run.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1586195

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This bug is also happening with Trusty and Wily?

Changed in linux (Ubuntu):
importance: Undecided → High
status: Incomplete → Triaged
Changed in linux (Ubuntu Xenial):
status: New → Triaged
importance: Undecided → High
tags: added: kernel-da-key xenial
Revision history for this message
Mike Gerow (gerow) wrote :

Yes, I've only specifically checked trusty, wily, and the 4.6 kernel from <http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D>.

Revision history for this message
Mike Gerow (gerow) wrote :

If it's any help at all: my personal laptop running Debian unstable doesn't seem to have the same issue with this device (it's on 4.5.0).

Also, this adapter specifically is the "Monoprice USB3.0 Gigabit Ethernet Adapter" <http://www.monoprice.com/product?p_id=11195>, which is Realtek 8153-based as the bug title mentions.

Revision history for this message
Mike Gerow (gerow) wrote :

And by "doesn't seem to have the same issue" I mean I still get the "Stop submitting intr, status -71" error when disconnecting the device, but it doesn't seem to randomly stop working between when I initially plug it in and some time in the future (probably averages around 15 minutes).

Revision history for this message
penalvch (penalvch) wrote :

Mike Gerow, could you please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1586195

Don't worry about timing this to immediately after it stopped working.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Ying-Chun Liu (paulliu) wrote :

Hi Mike,

I'm curious about your device. Can you paste a photo of your device?
It seems to me that for the same USB id 0bda:8153, some works perfect but some don't. They made by different vendors.

Revision history for this message
Mike Gerow (gerow) wrote :

Of course. The device itself doesn't have any interesting markings, but luckily I still have the packaging it came in too.

Revision history for this message
Mike Gerow (gerow) wrote :

And the other side.

Revision history for this message
zwpwjwtz (zwpwjwtz) wrote :

Similar problem, dmesg gives:

[ 15.229468] usb 3-1.1: new SuperSpeed USB device number 4 using xhci_hcd
[ 15.249257] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=8153
[ 15.249260] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 15.249262] usb 3-1.1: Product: USB 10/100/1000 LAN
[ 15.249264] usb 3-1.1: Manufacturer: Realtek
[ 15.249265] usb 3-1.1: SerialNumber: 000000000000
[ 15.329605] usb 3-1.1: reset SuperSpeed USB device number 4 using xhci_hcd
[ 15.372202] r8152 3-1.1:1.0 eth0: v1.08.2
[ 16.413210] r8152 3-1.1:1.0 enx00e04c680bfb: renamed from eth0
[ 16.454622] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680bfb: link is not ready
[ 17.032871] IPv6: ADDRCONF(NETDEV_UP): enx00e04c680bfb: link is not ready
[ 17.038222] usb 3-1.1: Disable of device-initiated U1 failed.
[ 17.038257] usb 3-1.1: Failed to set U2 timeout to 0x0,error code -71
[ 17.042065] usb 3-1.1: Set SEL for device-initiated U1 failed.
[ 17.045682] usb 3-1.1: Set SEL for device-initiated U2 failed.
[ 17.045690] usb 3-1.1: usb_reset_and_verify_device Failed to disable LPM
               .
[ 17.046906] usb 3-1.1: USB disconnect, device number 4
[ 17.713462] usb 3-1.1: new SuperSpeed USB device number 5 using xhci_hcd
[ 17.730139] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=8153
[ 17.730147] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 17.730151] usb 3-1.1: Product: USB 10/100/1000 LAN
[ 17.730155] usb 3-1.1: Manufacturer: Realtek
[ 17.730158] usb 3-1.1: SerialNumber: 000000000000
[ 22.732882] usb 3-1.1: Disable of device-initiated U1 failed.
[ 22.739551] usb 3-1.1: Disable of device-initiated U2 failed.
[ 23.053009] usb 3-1.1: reset SuperSpeed USB device number 5 using xhci_hcd

Using Ubuntu 16.04, kernel 4.4.0-28-generic. Also reproduced under Manjaro 16.08, kernel 4.7.2-1.

Revision history for this message
penalvch (penalvch) wrote :

zwpwjwtz, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
zwpwjwtz (zwpwjwtz) wrote :

I tested following versions of Ubuntu Live ISOs:

- 15.10 (kernel 4.2.0-16-generic)
- 15.04 (kernel 3.19.0-15-generic)
- 14.10 (kernel 3.16.0-23-generic)
- 14.04.5 (kernel 4.4.0-31-generic)

Both 15.04 and 14.10 work fine. But I noticed some differences showed in dmesg: "eth0" came up directly without being renamed to something like "enp0sXXXX".

penalvch (penalvch)
Changed in linux (Ubuntu Xenial):
status: Triaged → Incomplete
wolf (w+lf)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.]

Changed in linux (Ubuntu Xenial):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
htrex (hantarex) wrote :

I'm seeing this problem too on Ubuntu 16.04.2.
The same USB Ethernet adapter works reliably on the same laptop using Windows with no additional drivers.

uname -a
Linux OrionXPS 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5 09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

dmesg
[ 61.767587] usb 2-1.4: usb_reset_and_verify_device Failed to disable LTM
               .
[ 61.770131] usb 2-1.4: USB disconnect, device number 3
[ 62.450020] usb 2-1.4: new SuperSpeed USB device number 4 using xhci_hcd
[ 62.472325] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8153
[ 62.472327] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 62.472327] usb 2-1.4: Product: USB 10/100/1000 LAN
[ 62.472328] usb 2-1.4: Manufacturer: Realtek
[ 62.472329] usb 2-1.4: SerialNumber: 000001000000
[ 62.558798] usb 2-1.4: reset SuperSpeed USB device number 4 using xhci_hcd
[ 62.638859] r8152 2-1.4:1.0 eth0: v1.08.6
[ 64.163184] r8152 2-1.4:1.0 enx00e04c685fd5: renamed from eth0
[ 64.194844] IPv6: ADDRCONF(NETDEV_UP): enx00e04c685fd5: link is not ready
[ 64.225463] IPv6: ADDRCONF(NETDEV_UP): enx00e04c685fd5: link is not ready
[ 66.117694] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c685fd5: link becomes ready
[ 80.437996] NOHZ: local_softirq_pending 08
[ 97.549623] usb 2-1.4: usb_reset_and_verify_device Failed to disable LTM
               .
[ 97.552155] usb 2-1.4: USB disconnect, device number 4
[ 98.232089] usb 2-1.4: new SuperSpeed USB device number 5 using xhci_hcd
[ 98.253454] usb 2-1.4: New USB device found, idVendor=0bda, idProduct=8153
[ 98.253455] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 98.253456] usb 2-1.4: Product: USB 10/100/1000 LAN
[ 98.253456] usb 2-1.4: Manufacturer: Realtek
[ 98.253457] usb 2-1.4: SerialNumber: 000001000000
[ 98.340488] usb 2-1.4: reset SuperSpeed USB device number 5 using xhci_hcd
[ 98.420930] r8152 2-1.4:1.0 eth0: v1.08.6
[ 99.945849] r8152 2-1.4:1.0 enx00e04c685fd5: renamed from eth0
[ 99.968708] IPv6: ADDRCONF(NETDEV_UP): enx00e04c685fd5: link is not ready
[ 99.999171] IPv6: ADDRCONF(NETDEV_UP): enx00e04c685fd5: link is not ready
[ 101.883348] IPv6: ADDRCONF(NETDEV_CHANGE): enx00e04c685fd5: link becomes ready

Revision history for this message
htrex (hantarex) wrote :

In my case the device is an Ethernet + 3 usb port adapter.

Revision history for this message
penalvch (penalvch) wrote :

htrex, so your problem may be tracked, it will help immensely if you filed a new report with Ubuntu, using the default repository kernel (not mainline/upstream/3rd party) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Thiago Padilha (tpadilhacc) wrote :

The following workaround fixes for me: https://ubuntuforums.org/showthread.php?t=2226734

Here are the steps adapted for systemd:

- Check the output of `ls /sys/bus/pci/drivers/xhci_hcd`. In my laptop I see "0000:00:14.0 bind new_id remove_id uevent unbind". The goal is to get the id of the xhci_hcd, for me it is "0000:00:14.0"(which I will use in the following steps). Also verify that the output shows "bind" and "unbind" as directory entries. The following commands should be executed in a root shell

- Create a script to unbind the xhci:

    # cat > /usr/local/bin/unbind-xhci << "EOF"
    #!/bin/sh
    echo -n '0000:00:14.0' | tee /sys/bus/pci/drivers/xhci_hcd/unbind
    EOF
    # chmod +x /usr/local/bin/unbind-xhci

- Create a script to rebind the xhci:

    # cat > /usr/local/bin/rebind-xhci << "EOF"
    #!/bin/sh
    echo -n '0000:00:14.0' | tee /sys/bus/pci/drivers/xhci_hcd/bind
    EOF
    # chmod +x /usr/local/bin/rebind-xhci

- Create a systemd service that runs before sleep:

    # cat > /etc/systemd/system/unbind-xhci.service << "EOF"
    [Unit]
    Description=Unbind xHCI Host Controller Driver before sleep
    Before=sleep.target

    [Service]
    Type=oneshot
    ExecStart=/usr/local/bin/unbind-xhci

    [Install]
    WantedBy=sleep.target
    EOF

- Create a systemd service that runs after wakeup:

    # cat > /etc/systemd/system/rebind-xhci.service << "EOF"
    [Unit]
    Description=Unbind xHCI Host Controller Driver after wakeup
    After=suspend.target
    After=hibernate.target
    After=hybrid-sleep.target

    [Service]
    Type=oneshot
    ExecStart=/usr/local/bin/rebind-xhci

    [Install]
    WantedBy=suspend.target
    WantedBy=hibernate.target
    WantedBy=hybrid-sleep.target
    EOF

- Reload systemd

    # systemctl daemon-reload

Revision history for this message
Bougron (francis-bougron) wrote :

Hello
I have the same problem since 4 years!

I can perfectly use this key on a usb2 port.

I can not detect this key on a usb3 port. The dmesg command sees nothing at all!

But if I plug it with an adapter cable to the usb3 standard, it is seen but remains unusable.See file USB3.txt

However, the port works well with an another key of 16GB from the same manufacturer.

a@a:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
a@a:~$

Revision history for this message
penalvch (penalvch) wrote :

Bougron (francis-bougron), it most helpful if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Revision history for this message
Pablo Fontoura (pablofontoura) wrote :
Download full text (3.2 KiB)

Hi,

I have the same problem.
I can perfectly use this key on a usb2 port.
The usb3 port is working, i can use pendrive on this port.

The outputs when the key is plugged on usb3 are:

1) dmesg

[40261.131061] usb 2-1: new SuperSpeed USB device number 6 using xhci_hcd
[40261.152025] usb 2-1: New USB device found, idVendor=0bda, idProduct=8153
[40261.152035] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[40261.152042] usb 2-1: Product: USB 10/100/1000 LAN
[40261.152048] usb 2-1: Manufacturer: Realtek
[40261.152053] usb 2-1: SerialNumber: 000001000000
[40261.283522] usb 2-1: reset SuperSpeed USB device number 6 using xhci_hcd
[40261.345831] r8152 2-1:1.0 eth0: v1.09.9
[40261.407779] r8152 2-1:1.0 enx9cebe85eac03: renamed from eth0
[40261.433452] IPv6: ADDRCONF(NETDEV_UP): enx9cebe85eac03: link is not ready
[40261.437807] IPv6: ADDRCONF(NETDEV_UP): enx9cebe85eac03: link is not ready
[40261.471953] usb 2-1: USB disconnect, device number 6
[40261.472042] r8152 2-1:1.0 enx9cebe85eac03: Stop submitting intr, status -108

2) lspci

00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08)
00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

3) lsb_release -a

LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

4) uname -a

Linux xxx-inspiron 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

5) lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f3:2494 Elan Microelectronics Corp.
Bus 001 Device 004: ID 0cf3:e007 Atheros Communications, Inc.
Bus 001 Device 003: ID 0bda:58c2 Realtek Semiconductor Corp.
Bus 001 Device 024: ID 045e:0797 Microsoft Corp. Optical Mouse 200
Bus 001 Device 001: ...

Read more...

Ian! D. Allen (idallen)
Changed in linux (Ubuntu):
status: Expired → Confirmed
Ian! D. Allen (idallen)
tags: added: apport-collected bionic
Revision history for this message
penalvch (penalvch) wrote :

Ian! D. Allen (idallen)), it most helpful if you use the computer the problem is reproducible with, and provide necessary debugging logs by filing a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

tags: removed: apport-collected bionic
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.