Spent a LOT of time troubleshooting this. Had the same happen to mine. Then I stumbled upon this in the logs for Fedora, Ubuntu and other distros (logs varied a little between distros, but overall the same):
usb 2-3: USB disconnect, device number 74 xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. cdc_ncm 2-3:2.0 enx9cbf0d000e38: unregister 'cdc_ncm' usb-0000:00:0d.0-3, CDC NCM xhci_hcd 0000:00:0d.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
After seeing this happen on multiple Framework laptops, I tried it on another vendor’s laptop - same issue, same error.
Then I grabbed another USB to Ethernet with the exact same chipset/driver module used in the kernel - no errors, worked great.
After testing both the problem card and the third party dongle with the same hardware on multiple kernels and distros, I was able to compare this to the error seen with the bad card.
Then I grabbed an unopened, brand new Ethernet expansion card - no errors, no dropping, multiple distros, multiple kernels, all working.
So what’s the deal? The problem Ethernet expansion card was failing. Even more so, it was failing slowly and not all at once (for me).
TLTR: You will want to RMA the expansion card. It’s a bad card. What we believe was happening is the card state was being tweaked when any steady data was being pushed through it.
I can tell you that properly working Ethernet expansion cards work and work really well on Fedora and other distros. It’s a bad card. 