Realtek USB 2.5 Gbe - Random USB disconnect

C

chrisuan

New Member
Dec 16, 2023
3
1
3
Anyone else facing an issue with Proxmox VE 8.1.3 stability with Realtek USB-C 2.5GBe randomly disconnecting? After rebooting the Proxmox VE, everything works fine for x hours and sometimes it is good for the entire day, then I get the below message.

Can anyone help me if you have resolved this?

Dec 16 09:03:32 proxmox kernel: r8152-cfgselector 2-3: USB disconnect, device number 2
Dec 16 09:03:32 proxmox kernel: xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Dec 16 09:03:32 proxmox kernel: vmbr2: port 1(enx00e04c68001e) entered disabled state
Dec 16 09:03:32 proxmox kernel: r8152 2-3:1.0 enx00e04c68001e (unregistering): left allmulticast mode
Dec 16 09:03:32 proxmox kernel: r8152 2-3:1.0 enx00e04c68001e (unregistering): left promiscuous mode
Dec 16 09:03:32 proxmox kernel: vmbr2: port 1(enx00e04c68001e) entered disabled state
Dec 16 09:03:32 proxmox kernel: usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd
Dec 16 09:03:32 proxmox kernel: usb 2-3: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.04
Dec 16 09:03:32 proxmox kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Dec 16 09:03:32 proxmox kernel: usb 2-3: Product: USB 10/100/1G/2.5G LAN
Dec 16 09:03:32 proxmox kernel: usb 2-3: Manufacturer: Realtek
Dec 16 09:03:32 proxmox kernel: cdc_ncm 2-3:2.0: MAC-Address: --Omitted--
Dec 16 09:03:32 proxmox kernel: cdc_ncm 2-3:2.0: setting rx_max = 16384
Dec 16 09:03:32 proxmox kernel: cdc_ncm 2-3:2.0: setting tx_max = 16384
Dec 16 09:03:32 proxmox kernel: cdc_ncm 2-3:2.0 eth0: register 'cdc_ncm' at usb-0000:00:0d.0-3, CDC NCM (NO ZLP), --Omitted--
Dec 16 09:03:32 proxmox kernel: cdc_ncm 2-3:2.0 eth0: unregister 'cdc_ncm' usb-0000:00:0d.0-3, CDC NCM (NO ZLP)
Dec 16 09:03:33 proxmox kernel: r8152-cfgselector 2-3: reset SuperSpeed USB device number 3 using xhci_hcd
Dec 16 09:03:33 proxmox kernel: r8152 2-3:1.0: load rtl8156b-2 v3 10/20/23 successfully
Dec 16 09:03:33 proxmox kernel: r8152 2-3:1.0 eth0: v1.12.13
Dec 16 09:03:33 proxmox kernel: usbcore: registered new interface driver cdc_wdm
Dec 16 09:03:33 proxmox kernel: usbcore: registered new interface driver cdc_mbim
Dec 16 09:03:33 proxmox kernel: r8152 2-3:1.0 enx00e04c68001e: renamed from eth0
 
Last edited:
Yes, I have three lab Firebats AK2 and one of them is showing the behaviour. The difference is kernel - the two working fine are on: 6.5.11-6-pve, the one with the problem on: 6.5.11-7-pve. But the problematic machine is also a fresh install...

Tried so far with no luck
1. Swapping the USB cards around
2. Having two of them in USB 3.0 ports
3. Setting the /sys/module/usbcore/parameters/autosuspend to -1
4. Using the the 50-usb dev rule and alternative driver - same thing happens

Now trying the sg off... Will get back to you. USB qurics are next

In my setup I get that quite often - like every couple of hours... Not much traffic is flowing tru that NIC yet, machine is empty.
 
Last edited:
OK, after couple of days I can say that the quickrs fixed my issue: Add kernel boot option in
Code: 
/etc/defaults/grub
, similar to:
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet usbcore.autosuspend=-1 usbcore.quirks=0bda:8156:k"

OP, if it works for you too - please edit the thread topic to [SOLVED], thanks!
 
  • Like
Reactions: chrisuan
lukaszjokiel said:
OK, after couple of days I can say that the quickrs fixed my issue: Add kernel boot option in
Code: 
/etc/defaults/grub
, similar to:
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet usbcore.autosuspend=-1 usbcore.quirks=0bda:8156:k"

OP, if it works for you too - please edit the thread topic to [SOLVED], thanks!
Click to expand...
Oh that's great to hear, although I haven't re-tried it yet as I have removed the node and migrated everything onto a new node with 2x 2.5GBe NICs. I'll give it a shot this weekend. Thank you for looking into this though which hopefully will help the rest of the community.
 
  • Like
Reactions: lukaszjokiel
I have the same problem, but it does not work for me...
Even with both entries in the /etc/defaults/grub does not help.
What helps for the moment (instead of reboot):
service networking restart

But if it happens while backups are running, the backup stucks and blocks the complete server.

So it is no option to script sth which "looks" for the error and restarts the network service...

Sometimes the system is running for 3 or 4 days and sometimes it happens 2 times a day.

Does anyone have more ideas?


My setup:
Framework Laptop 13 Mainboard (11th Gen Intel® Core™) - i7-1165G7 with 64GB RAM
Coolermaster Case (no Laptop-Case)
3 USB-C addon cards:
HDMI, USB-C (for charging), USB-A (for keyboard) and Realtek Network Card 2,5Gbit

The server is connected to a Ubiquiti Unifi environment. It is connected to a 2,5Gbit port on a USW Enterprise 8 PoE Switch.
The problems occurs since the kernel update in october or november 2023 (not exactly sure when it released / I installed it).



Here is some more output:

Proxmox Virtual Environment 8.1.4

Code: 
uname -a
Linux server 6.5.11-7-pve #1 SMP PREEMPT_DYNAMIC PMX 6.5.11-7 (2023-12-05T09:44Z) x86_64 GNU/Linux


Code: 
lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 32ac:0002 Framework HDMI Expansion Card
Bus 003 Device 004: ID 24ae:1007 Shenzhen Rapoo Technology Co., Ltd. Rapoo 2.4G Wireless Device
Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 0bda:8156 Realtek Semiconductor Corp. USB 10/100/1G/2.5G LAN
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Code: 
SYSLOG
Jan 26 22:10:01 server kernel: r8152-cfgselector 2-2: USB disconnect, device number 2
Jan 26 22:10:01 server kernel: xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 26 22:10:01 server kernel: vmbr0: port 1(enx9cbf0d00392b) entered disabled state
Jan 26 22:10:01 server kernel: r8152 2-2:1.0 enx9cbf0d00392b (unregistering): left allmulticast mode
Jan 26 22:10:01 server kernel: r8152 2-2:1.0 enx9cbf0d00392b (unregistering): left promiscuous mode
Jan 26 22:10:01 server kernel: vmbr0: port 1(enx9cbf0d00392b) entered disabled state
Jan 26 22:10:02 server kernel: usb 2-2: new SuperSpeed USB device number 3 using xhci_hcd
Jan 26 22:10:02 server kernel: usb 2-2: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.04
Jan 26 22:10:02 server kernel: usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
Jan 26 22:10:02 server kernel: usb 2-2: Product: USB 10/100/1G/2.5G LAN
Jan 26 22:10:02 server kernel: usb 2-2: Manufacturer: Realtek
Jan 26 22:10:02 server kernel: usb 2-2: SerialNumber: 4013000001
Jan 26 22:10:02 server kernel: cdc_ncm 2-2:2.0: MAC-Address: 9c:bf:0d:00:39:2b
Jan 26 22:10:02 server kernel: cdc_ncm 2-2:2.0: setting rx_max = 16384
Jan 26 22:10:02 server kernel: cdc_ncm 2-2:2.0: setting tx_max = 16384
Jan 26 22:10:02 server kernel: cdc_ncm 2-2:2.0 eth0: register 'cdc_ncm' at usb-0000:00:0d.0-2, CDC NCM (NO ZLP), 9c:bf:0d:00:39:2b
Jan 26 22:10:02 server kernel: cdc_ncm 2-2:2.0 eth0: unregister 'cdc_ncm' usb-0000:00:0d.0-2, CDC NCM (NO ZLP)
Jan 26 22:10:02 server kernel: r8152-cfgselector 2-2: reset SuperSpeed USB device number 3 using xhci_hcd
Jan 26 22:10:02 server kernel: r8152 2-2:1.0: load rtl8156b-2 v3 10/20/23 successfully
Jan 26 22:10:02 server kernel: r8152 2-2:1.0 eth0: v1.12.13
Jan 26 22:10:02 server kernel: usbcore: registered new interface driver cdc_wdm
Jan 26 22:10:02 server kernel: usbcore: registered new interface driver cdc_mbim
Jan 26 22:10:02 server kernel: r8152 2-2:1.0 enx9cbf0d00392b: renamed from eth0

This happened with the kernel boot option in "/etc/default/grub"


Code: 
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet usbcore.autosuspend=-1 usbcore.quirks=0bda:8156:k"
GRUB_CMDLINE_LINUX=""

and the value "on" in the file "/sys/bus/usb/devices/2-2/power/control".
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back