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:
Sorry for my late reply.
It worked - I just forgot to update GRUB... I know - nothing more to say ;-)

System is absolut stable since the change and I am very happy with this setup.
So thank you for your help.
 
  • Like
Reactions: lukaszjokiel
ncsemke said:
Sorry for my late reply.
It worked - I just forgot to update GRUB... I know - nothing more to say ;-)

System is absolut stable since the change and I am very happy with this setup.
So thank you for your help.
Click to expand...
So what exactly was the solution? I just got a Framework Ethernet expansion card as I wanted to convert my old laptop into a server and I'm having the same issue.
 
Is this a bug which may end up being patched long term?
I just picked one of these up to test another issue and found this thing vastly worse than the e1000e I was diagnosing a major problem with.

I tested the USB adapter today in the office on a Windows machine for hours without issue.
It's an "rtl8156b-2" "v3"
v1.12.13

I also tested it on Linux Mint for about an hour without any issue either.
 
Here's a pic of the error on proxmox at the bottom, can recreate very very quickly unfortunately.
Here's the text from the console showing it quickly failing on proxmox


[ 12.319546] vmbro: port 1 (enx98e743XXXXXXXX) entered forwarding state
[ 12.373328] RPC: Registered named UNIX socket transport module.
[ 12.373995] RPC: Registered udp transport module.
[ 12.374662] RPC: Registered tcp transport module.
[ 12.375316] RPC: Registered tcp-with-tls transport module.
[ 12.375962] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 12.494563] r8152 4-2:1.0 enx98e74XXXXXXXX: Promiscuous mode enabled
[ 12.495347] r8152 4-2:1.0 enx98e74XXXXXXXX: carrier on
[ 25.148638] kvm_intel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin
[ 213.197761] vmbro: port 1 (enx98e74XXXXXXXX) entered disabled state
[ 213.200924] r8152 4-2:1.0 enx98e74XXXXXXXX: carrier off
[ 249.042084] r8152 4-2:1.0 enx98e7XXXXXXXX: Promiscuous mode enabled
[ 249.042183] r8152 4-2:1.0 enx98e743XXXXXXXX: carrier on
[ 249.042559] vmbro: port 1 (enx98e74XXXXXXXX) entered blocking state
[ 249.042571] vmbro: port 1 (enx98e743XXXXXXXX) entered forwarding state
[ 1476.067473] r8152-cfgselector 4-2: USB disconnect, device number 2
[ 1476.067707] xhci_hcd 0000:39:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
[ 1476.067807] vmbro: port 1 (enx98e743XXXXXXXX) entered disabled state
[ 1476.068169] r8152 4-2:1.0 enx98e74XXXXXXXX (unregistering): left allmulticast mode
[ 1476.068185] r8152 4-2:1.0 enx98e743bXXXXXXXX (unregistering): left promiscuous mode
[ 1476.068198] vmbro: port 1 (enx98e743XXXXXXXX) entered disabled state
[ 1476.317475] usb 4-2: new SuperSpeed USB device number 3 using xhci_hcd
[ 1476.330207] usb 4-2: New USB device found, idvendor=0bda, idProduct=8156, bcdDevice=31.04
[ 1476.330230] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 1476.330242] usb 4-2: Product: USB 10/100/1G/2.5G LAN
[ 1476.330252] usb 4-2: Manufacturer: Realtek
[ 1476.330261] usb 4-2: SerialNumber: XXXXXXXX
[ 1476.447208] r8152-cfgselector 4-2: reset SuperSpeed USB device number 3 using xhci_hcd ): Using pass-thru MAC addr 98:e7:XXXXXXXXX
[ 1476.463545] r8152 4-2:1.0 (unnamed net_device) (uninitialized
[ 1476.534845] r8152 4-2:1.0: load rt18156b-2 v3 10/20/23 successfully
[ 1476.567662] r8152 4-2:1.0 eth0: v1.12.13
[ 1476.572907] r8152 4-2:1.0 enx98e74XXXXXXXX: renamed from ethe
[ 1476.572907] r8152 4-2:1.0 enx98e74XXXXXXXX: renamed from ethe
Click to expand...


https://i.imgur.com/UNqd3sq.png

I hope this helps others finding this thread, that being said it would be nice if this could be addressed with a more perm solution, any ideas how how this might occur?
Thank you all.
 
Last edited:
Here's a good portion of the string from USBView as well:


=========================== USB Port15 ===========================

Connection Status : 0x01 (Device is connected)
Port Chain : 2-15
Properties : 0x03
IsUserConnectable : yes
PortIsDebugCapable : yes
PortHasMultiCompanions : no
PortConnectorIsTypeC : no
ConnectionIndex : 0x0F (Port 15)
CompanionIndex : 0
CompanionHubSymLnk : USB#ROOT_HUB30#4&ffebd38&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
CompanionPortNumber : 0x04 (Port 4)
-> CompanionPortChain : 2-4

========================== Summary =========================
Vendor ID : 0x0BDA (Realtek Semiconductor Corp.)
Product ID : 0x8156
USB Version : 3.2 Gen 1
Port maximum Speed : SuperSpeed
Device maximum Speed : SuperSpeed
Device Connection Speed : SuperSpeed
Self powered : no
Demanded Current : 256 mA
Used Endpoints : 4

======================== USB Device ========================

+++++++++++++++++ Device Information ++++++++++++++++++
Friendly Name : Realtek Gaming USB 2.5GbE Family Controller
Device Description : Realtek Gaming USB 2.5GbE Family Controller
Device Path 1 : \\?\USB#VID_0BDA&PID_8156#4013000001#{a5dcbf10-6530-11d2-901f-00c04fb951ed} (GUID_DEVINTERFACE_USB_DEVICE)
Device Path 2 : \\?\USB#VID_0BDA&PID_8156#4013000001#{ad498944-762f-11d0-8dcb-00c04fc3358c}\{9a96ed95-5428-4405-8011-72ec5f30391d} (GUID_NDIS_LAN_CLASS)
Device Path 3 : \\?\USB#VID_0BDA&PID_8156#4013000001#{cac88484-7515-4c03-82e6-71a87abac361} (GUID_DEVINTERFACE_NET)
Kernel Name : \Device\USBPDO-15
Device ID : USB\VID_0BDA&PID_8156\4013000001
Hardware IDs : USB\VID_0BDA&PID_8156&REV_3104 USB\VID_0BDA&PID_8156
Driver KeyName : {4d36e972-e325-11ce-bfc1-08002be10318}\0028 (GUID_DEVCLASS_NET)
Driver : \SystemRoot\System32\drivers\rtump64x64.sys (Version: 10.52.418.2022 Date: 2022-05-13)
Driver Inf : C:\WINDOWS\inf\oem44.inf
Legacy BusType : PNPBus
Class : Net
Class GUID : {4d36e972-e325-11ce-bfc1-08002be10318} (GUID_DEVCLASS_NET)
Service : rtump64x64
Enumerator : USB
Location Info : Port_#0015.Hub_#0002
Location IDs : PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(15), ACPI(_SB_)#ACPI(PC00)#ACPI(XHCI)#ACPI(RHUB)#ACPI(SS03)
Container ID : {3e4adce0-1043-5c3b-a7aa-2ba563c3fc67}
Manufacturer Info : Realtek
Capabilities : 0x94 (Removable, UniqueID, SurpriseRemovalOK)
Status : 0x0180600A (DN_DRIVER_LOADED, DN_STARTED, DN_DISABLEABLE, DN_REMOVABLE, DN_NT_ENUMERATOR, DN_NT_DRIVER)
Problem Code : 0
Power State : D0 (supported: D0, D1, D2, D3, wake from D0, wake from D1, wake from D2)

+++++++++++++++++ Registry USB Flags +++++++++++++++++
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0BDA81563104
osvc : REG_BINARY 00 00

---------------- Connection Information ---------------
Connection Index : 0x0F (Port 15)
Connection Status : 0x01 (DeviceConnected)
Current Config Value : 0x01 (Configuration 1)
Device Address : 0x18 (24)
Is Hub : 0x00 (no)
Device Bus Speed : 0x02 (High-Speed) -> not true, see below in Connection Information V2
Number Of Open Pipes : 0x03 (3 pipes to data endpoints)
Pipe[0] : EndpointID=1 Direction=IN ScheduleOffset=0 Type=Bulk wMaxPacketSize=0x400 bInterval=0
Pipe[1] : EndpointID=2 Direction=OUT ScheduleOffset=0 Type=Bulk wMaxPacketSize=0x400 bInterval=0
Pipe[2] : EndpointID=3 Direction=IN ScheduleOffset=0 Type=Interrupt wMaxPacketSize=0x2 bInterval=11 -> 140 Bits/ms = 17500 Bytes/s
Data (HexDump) : 0F 00 00 00 12 01 20 03 00 00 00 09 DA 0B 56 81 ...... .......V.
04 31 01 02 06 03 01 02 00 18 00 03 00 00 00 01 .1..............
00 00 00 07 05 81 02 00 04 00 00 00 00 00 07 05 ................
02 02 00 04 00 00 00 00 00 07 05 83 03 02 00 0B ................
00 00 00 00 ....

--------------- Connection Information V2 -------------
Connection Index : 0x0F (15)
Length : 0x10 (16 bytes)
SupportedUsbProtocols : 0x04
Usb110 : 0 (no, port not supports USB 1.1) -> but Companion Port 2-4 does
Usb200 : 0 (no, port not supports USB 2.0) -> but Companion Port 2-4 does
Usb300 : 1 (yes, port supports USB 3.0)
ReservedMBZ : 0x00
Flags : 0x03
DevIsOpAtSsOrHigher : 1 (Device is operating at SuperSpeed or higher)
DevIsSsCapOrHigher : 1 (Device is SuperSpeed capable or higher)
DevIsOpAtSsPlusOrHigher : 0 (Device is not operating at SuperSpeedPlus or higher)
DevIsSsPlusCapOrHigher : 0 (Device is not SuperSpeedPlus capable or higher)
ReservedMBZ : 0x00
Data (HexDump) : 0F 00 00 00 10 00 00 00 04 00 00 00 03 00 00 00 ................

---------------------- Device Descriptor ----------------------
bLength : 0x12 (18 bytes)
bDescriptorType : 0x01 (Device Descriptor)
bcdUSB : 0x320 (USB Version 3.2)
bDeviceClass : 0x00 (defined by the interface descriptors)
bDeviceSubClass : 0x00
bDeviceProtocol : 0x00
bMaxPacketSize0 : 0x09 (9 bytes)
idVendor : 0x0BDA (Realtek Semiconductor Corp.)
idProduct : 0x8156
bcdDevice : 0x3104
iManufacturer : 0x01 (String Descriptor 1)
Language 0x0409 : "Realtek"
iProduct : 0x02 (String Descriptor 2)
Language 0x0409 : "USB 10/100/1G/2.5G LAN"
iSerialNumber : 0x06 (String Descriptor 6)
Language 0x0409 : "4013000001"
bNumConfigurations : 0x03 (3 Configurations)
Data (HexDump) : 12 01 20 03 00 00 00 09 DA 0B 56 81 04 31 01 02 .. .......V..1..
06 03 ..

------------------ Configuration Descriptor -------------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x02 (Configuration Descriptor)
wTotalLength : 0x0039 (57 bytes)
bNumInterfaces : 0x01 (1 Interface)
bConfigurationValue : 0x01 (Configuration 1)
iConfiguration : 0x00 (No String Descriptor)
bmAttributes : 0xA0
D7: Reserved, set 1 : 0x01
D6: Self Powered : 0x00 (no)
D5: Remote Wakeup : 0x01 (yes)
D4..0: Reserved, set 0 : 0x00
MaxPower : 0x20 (256 mA)
Data (HexDump) : 09 02 39 00 01 01 00 A0 20 09 04 00 00 03 FF FF ..9..... .......
00 00 07 05 81 02 00 04 00 06 30 03 00 00 00 07 ..........0.....
05 02 02 00 04 00 06 30 03 00 00 00 07 05 83 03 .......0........
02 00 0B 06 30 00 00 02 00 ....0....

---------------- Interface Descriptor -----------------
bLength : 0x09 (9 bytes)
bDescriptorType : 0x04 (Interface Descriptor)
bInterfaceNumber : 0x00 (Interface 0)
bAlternateSetting : 0x00
bNumEndpoints : 0x03 (3 Endpoints)
bInterfaceClass : 0xFF (Vendor Specific)
bInterfaceSubClass : 0xFF
bInterfaceProtocol : 0x00
iInterface : 0x00 (No String Descriptor)
Data (HexDump) : 09 04 00 00 03 FF FF 00 00 .........
Click to expand...
 
ncsemke said:
and the value "on" in the file "/sys/bus/usb/devices/2-2/power/control".
Click to expand...

Hi, sorry to revive this thread - I am having similar issues and have added the changes to GRUB
Not sure I understand what you mean with this instruction, could you please elaborate what I should do here?
Many thanks
 
If
Code: 
proxmox-boot-tool status
shows your system boots from UEFI, then the options should be in
Code: 
/etc/kernel/cmdline
You can check if option is taken into account :

Code: 
# cat /sys/module/usbcore/parameters/autosuspend
-1
 
  • Like
Reactions: why-be-banned
I just wanted to share my experience.

After a power cut, my Dell Micro 5090 was never able to maintain its USB/Ethernet 2.5G connection for more than a few minutes (which I had switched to, in order to replace the E1000 issues I was facing). Reinstalling Proxmox didn’t help. After trying multiple solutions, the only fix that worked for me was adding GRUB_CMDLINE_LINUX_DEFAULT="quiet usbcore.autosuspend=-1 usbcore.quirks=0bda:8156:k" as mentioned earlier. A big thank you to lukaszjokiel

It's crazy that this issue has been ongoing since at least 2019 (Realtek only?).
 
  • Like
Reactions: lukaszjokiel
Zearth said:
I just wanted to share my experience.

After a power cut, my Dell Micro 5090 was never able to maintain its USB/Ethernet 2.5G connection for more than a few minutes (which I had switched to, in order to replace the E1000 issues I was facing). Reinstalling Proxmox didn’t help. After trying multiple solutions, the only fix that worked for me was adding GRUB_CMDLINE_LINUX_DEFAULT="quiet usbcore.autosuspend=-1 usbcore.quirks=0bda:8156:k" as mentioned earlier. A big thank you to lukaszjokiel

It's crazy that this issue has been ongoing since at least 2019 (Realtek only?).
Click to expand...

Great that it still helps - I'm not really having any issues on latest 8.2 Proxmox kernels anymore.
 
kenji said:
If
Code: 
proxmox-boot-tool status
shows your system boots from UEFI, then the options should be in
Code: 
/etc/kernel/cmdline
You can check if option is taken into account :

Code: 
# cat /sys/module/usbcore/parameters/autosuspend
-1
Click to expand...

works for me on PVE8.3
 
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