usb networking adapter problem and replunging adapter doesn't reconnect networking.

shisui

Member
Dec 12, 2020
3
0
6
29
I have been struggling with networking problems for a long time.

Since the on-board NIC only supports 100M, so I bought a 2.5G usb nic with a r8156 chipset.

However, after an update, the network will randomly disconnect, and I must restart the device or the networking service.

my networking configuration:

Code:
auto lo
iface lo inet loopback

auto enp1s0
auto enx00e04c681128

auto vmbr0
iface vmbr0 inet static
        address 192.168.8.254/24
        gateway 192.168.8.1
        bridge-ports enx00e04c681128
        bridge-stp off
        bridge-fd 0
        bridge-vlan-aware yes
        bridge-vids 2-4094

I checked the logs and found the adapter was disconnected, enx00e04c681128 is the name of NIC.


Code:
Feb 07 11:23:15 pve pvedaemon[3868]: <root@pam> successful auth for user 'root@pam'
Feb 07 11:23:27 pve systemd-networkd[1802]: enx00e04c681128: Link DOWN
Feb 07 11:23:27 pve systemd-networkd[1802]: enx00e04c681128: Lost carrier
Feb 07 11:23:27 pve kernel: usb 2-4: USB disconnect, device number 2
Feb 07 11:23:27 pve kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Feb 07 11:23:27 pve kernel: cdc_ncm 2-4:2.0 enx00e04c681128: unregister 'cdc_ncm' usb-0000:00:14.0-4, CDC NCM
Feb 07 11:23:27 pve kernel: xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Feb 07 11:23:27 pve kernel: vmbr0: port 1(enx00e04c681128) entered disabled state
Feb 07 11:23:27 pve kernel: device enx00e04c681128 left promiscuous mode
Feb 07 11:23:27 pve kernel: vmbr0: port 1(enx00e04c681128) entered disabled state


then I found this:

xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state

xhci_hcd 0000:15:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state

A kernel bug.

After the network adapter reconnected, the networking still does not work until I restart the networking service.

Code:
Feb 07 11:23:27 pve kernel: usb 2-4: new SuperSpeed USB device number 3 using xhci_hcd
Feb 07 11:23:27 pve kernel: usb 2-4: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.00
Feb 07 11:23:27 pve kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Feb 07 11:23:27 pve kernel: usb 2-4: Product: USB 10/100/1G/2.5G LAN
Feb 07 11:23:27 pve kernel: usb 2-4: Manufacturer: Realtek
Feb 07 11:23:27 pve kernel: usb 2-4: SerialNumber: 001000001
Feb 07 11:23:27 pve kernel: cdc_ncm 2-4:2.0: MAC-Address: 00:e0:4c:68:11:28
Feb 07 11:23:27 pve kernel: cdc_ncm 2-4:2.0: setting rx_max = 16384
Feb 07 11:23:27 pve kernel: cdc_ncm 2-4:2.0: setting tx_max = 16384
Feb 07 11:23:27 pve kernel: cdc_ncm 2-4:2.0 eth0: register 'cdc_ncm' at usb-0000:00:14.0-4, CDC NCM, 00:e0:4c:68:11:28
Feb 07 11:23:27 pve systemd-udevd[29940]: Using default interface naming scheme 'v247'.
Feb 07 11:23:27 pve systemd-udevd[29940]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 07 11:23:27 pve kernel: cdc_ncm 2-4:2.0 enx00e04c681128: renamed from eth0
Feb 07 11:23:27 pve systemd-networkd[1802]: eth0: Interface name change detected, eth0 has been renamed to enx00e04c681128.
Feb 07 11:23:27 pve systemd-udevd[29940]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Feb 07 11:24:20 pve systemd-timesyncd[2856]: Timed out waiting for reply from 94.237.64.20:123 (0.debian.pool.ntp.org).
Feb 07 11:24:30 pve systemd-timesyncd[2856]: Timed out waiting for reply from 119.28.183.184:123 (0.debian.pool.ntp.org).
Feb 07 11:24:40 pve systemd-timesyncd[2856]: Timed out waiting for reply from 185.209.85.222:123 (0.debian.pool.ntp.org).
Feb 07 11:24:50 pve systemd-timesyncd[2856]: Timed out waiting for reply from 5.79.108.34:123 (0.debian.pool.ntp.org).
Feb 07 11:25:01 pve CRON[32316]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Feb 07 11:25:01 pve CRON[32371]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 07 11:25:01 pve CRON[32316]: pam_unix(cron:session): session closed for user root
Feb 07 11:25:52 pve npc[3250]: 2022/02/07 11:25:52 close mux


And replunging network cable doesn't reconnect networking.

I wonder if there is any solution.
Thanks in advance.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!