[RESPONDED] LAN module intermittently disconnecting from USB

  • Which OS (Operating System)?
    Proxmox VE
  • Which release of your OS (Operating System / Windows 10, 11, Distribution of Linux)?
    Proxmox VE 8.0-2
  • Which Framework laptop (11th, 12th or 13th generation Framework laptop) are you asking for support with?
    11th Gen (i7-1165G7) stand-alone in CoolerMaster case

Hi all,

I have 2 11th gen mainboards, both i7-1165G7 that I have set up as a Proxmox cluster.
They both have the LAN module installed and are working fine when booting up.
Then every once in a while (could be every other day, daily, or even more frequent) the server stops showing up on the network (not detected in router, no IP). After a reboot I check syslog and it mentions that the LAN module disconnects from USB, and a bit later it is re-detected by the OS but it is not active as my router doesn’t detect it and it’s not given an IP.
The activity lights on the module do keep blinking though.

I initially thought it was just 1 mainboard or 1 LAN adapter as the 2nd system stayed online at first but then it also started showing the same issues late last week.
Both mainboards are updated to the latest BIOS, and I have tried plugging in the LAN module on the different USB-C ports, to no avail.
Has anyone else ever faced an issue like this before, and is there perhaps a workaround so I could have a script that detects when this happens and resets the networkstack or such? I’m pretty new to Proxmox and Linux in general, especially when it comes to hardware monitoring and activating networkdevices/restarting services so if anyone could advise, that would be greatly appreciated.

1 Like

I just checked syslog again for the timings, and it’s really disconnecting & reconnecting within 1 second…

As an example from syslog:

Nov 09 05:26:28 pve-node01 kernel: r8152-cfgselector 2-2: USB disconnect, device number 3
Nov 09 05:26:29 pve-node01 kernel: usb 2-2: new SuperSpeed USB device number 4 using xhci_hcd
Nov 09 05:26:29 pve-node01 kernel: usb 2-2: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.04
Nov 09 05:26:29 pve-node01 kernel: usb 2-2: New USB device strings: Mfr=x, Product=x, SerialNumber=x
Nov 09 05:26:29 pve-node01 kernel: usb 2-2: Product: USB 10/100/1G/2.5G LAN
Nov 09 05:26:29 pve-node01 kernel: usb 2-2: Manufacturer: Realtek
Nov 09 05:26:29 pve-node01 kernel: usb 2-2: SerialNumber: xxxxxxxxxx
Nov 09 05:26:29 pve-node01 kernel: cdc_ncm 2-2:2.0: MAC-Address: xx:xx:xx:xx:xx:xx
Nov 09 05:26:29 pve-node01 kernel: cdc_ncm 2-2:2.0: setting rx_max = 16384
Nov 09 05:26:29 pve-node01 kernel: cdc_ncm 2-2:2.0: setting tx_max = 16384
Nov 09 05:26:29 pve-node01 kernel: cdc_ncm 2-2:2.0 eth0: register ‘cdc_ncm’ at usb-0000:00:0d.0-2, CDC NCM (NO ZLP), xx:xx:xx:xx:xx:xx
Nov 09 05:26:29 pve-node01 kernel: cdc_ncm 2-2:2.0 eth0: unregister ‘cdc_ncm’ usb-0000:00:0d.0-2, CDC NCM (NO ZLP)
Nov 09 05:26:29 pve-node01 kernel: r8152-cfgselector 2-2: reset SuperSpeed USB device number 4 using xhci_hcd
Nov 09 05:26:29 pve-node01 kernel: r8152 2-2:1.0: ram code speedup mode fail
Nov 09 05:26:29 pve-node01 kernel: r8152 2-2:1.0: load rtl8156b-2 v2 04/27/23 successfully
Nov 09 05:26:29 pve-node01 kernel: r8152 2-2:1.0 eth0: v1.12.13
Nov 09 05:26:29 pve-node01 kernel: r8152 2-2:1.0 enx9cbf0d00213f: renamed from eth0

1 Like

I’ve seen this before, specifically on distros with a lot of activity - it’s not as it should be.

Test this please, live Fedora USB (for testing), playing YouTube and pinging something like yahoo for a few minutes. Wifi off. You should see the drop happen. If you do, it’s the card, then open a ticket linking to this thread for context.

I’ve been running into this issue for some time, good to know I’m not the only one!

1 Like

Me too

All, in dmesg or journalctl, we’re looking for:

cdc_ncm 2-2:2.0 eth0: unregister ‘cdc_ncm’ usb-0000:00:0d.0-2, CDC NCM (NO ZLP)

We can use grep to look for this:

dmesg | grep "CDC NCM (NO ZLP)"

If you have trouble, try narrowing it down:

dmesg | grep "ZLP"

If you do find CDC NCM (NO ZLP), please open a support ticket.