Network Adapter in Thunderbold3 Dock don't work after Kernel 4.15.0-58

Bug #1843570 reported by Nein
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-signed-hwe (Ubuntu)
New
Undecided
Unassigned

Bug Description

Thunderbold Dock: Lenovo ThinkPad Thunderbolt 3 Gen 2

Problem: After updating my kernel to 4.15.0-60 the ethernet port don't work anymore. I hoped i can fix this with updating to kernel 5.sth.
The network adapter still don't work. When booting with 4.15.0-58 everything works fine.

Description: Ubuntu 18.04.3 LTS
Release: 18.04
Kernel: 5.0.0-27-generic (but don't matter)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.0.0-27-generic 5.0.0-27.28~18.04.1
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 11 13:35:46 2019
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Nein (obstschale) wrote :
Revision history for this message
gnomed (the-gnomed) wrote :
Download full text (6.5 KiB)

I submitted a detailed question to askubuntu.com with no responses (even after a bounty)

Here are the details it included:

Currently having major issues with thunderbolt ethernet adapter.

The device is a "Razer Core X" thunderbolt eGPU enclosure which has a built in USB3 hub and gigabit ethernet port. Essentially a very powerful dock with its own GPU (utilizing the 4 lanes of PCIe on the thunderbolt port).

The same issue occurs if I use the built in ethernet port or if I plug in my own USB3 ethernet adaptor into the USB3 hub on the dock. The issue does not occur if I bypass the thunderbolt dock and plug an ethernet adaptor in directly (although this kind of defeats the purpose of the dock).

The same issue also occurs on different laptops that both use this dock. My work laptop is on 18.04 and my new personal laptop is on 20.04 and both versions of Ubuntu on both laptops have the exact same behavior.

When the ethernet fails it is no longer able to resolve DNS nor can I even ping anything on my local network, but the device still appears "connected" in the NetworkManager UI. When I toggle the connection off/on then it shows "Connecting" and stays stuck there permanently.

When I check dmesg/syslog I see the exact same bunch of errors every single time. Below is an example of the error. Here you can see in the logs I reload the driver via modprobe which causes connection to work again briefly. Then the exact same error and symptoms occur moments later:

```
[SAME ERROR REPEATED ~20 times]
[ 543.814402] xhci_hcd 0000:0c:00.0: Looking for event-dma 0000000425e6e3f0 trb-start 0000000425e6e2e0 trb-end 0000000425e6e2e0 seg-start 0000000425e6e000 seg-end 0000000425e6eff0
[ 543.815185] xhci_hcd 0000:0c:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 543.815186] xhci_hcd 0000:0c:00.0: Looking for event-dma 0000000425e6e400 trb-start 0000000425e6e2e0 trb-end 0000000425e6e2e0 seg-start 0000000425e6e000 seg-end 0000000425e6eff0
[ 543.815271] xhci_hcd 0000:0c:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 543.815272] xhci_hcd 0000:0c:00.0: Looking for event-dma 0000000425e6e410 trb-start 0000000425e6e2e0 trb-end 0000000425e6e2e0 seg-start 0000000425e6e000 seg-end 0000000425e6eff0
[ 543.815356] xhci_hcd 0000:0c:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 543.815357] xhci_hcd 0000:0c:00.0: Looking for event-dma 0000000425e6e420 trb-start 0000000425e6e2e0 trb-end 0000000425e6e2e0 seg-start 0000000425e6e000 seg-end 0000000425e6eff0
[ 543.815822] xhci_hcd 0000:0c:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 543.815823] xhci_hcd 0000:0c:00.0: Looking for event-dma 0000000425e6e430 trb-start 0000000425e6e2e0 trb-end 0000000425e6e2e0 seg-start 0000000425e6e000 seg-end 0000000425e6eff0
[ 609.127969] usbcore: deregistering interface driver ax88179_178a
[ 609.128443] ax88179_178a 10-1:1.0 enx90203a1c2b65: unregister 'ax88179_178a' usb-0000:0c:00.0-1, ASIX AX88179 USB 3.0 Gigabit Ethernet
[ 609.643604] ax88179_178a 10-1:1.0 eth0: register 'ax88179_178a' at usb-0000:0c:00.0-1, ASIX AX881...

Read more...

Revision history for this message
gnomed (the-gnomed) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.