Networking through Thunderbolt 3 Gen 2 stops working after a while

[Peder Stray]

After booting into 5.3.0-26 on my Lenovo X390, it has started to loose network connection when connected to the Thunderbolt 3 Gen 2 dock after a while. It varies how long it takes, but anywhere from quite fast after boot to several hours of uptime. Suddenly no traffic goes through the interface in the dock, but the device seems to be up. Enabling wifi after it happens works fine, but unselecting "Enable Networking" in network manager, or quitting it, makes the whole computer hang (can move mouse, but no input from keyboard is registered anymore, or so it seems at least)

Rebooting after it happens requires hard reset, as nothing happens after Network Manager should stop.

Probably related to the patch introduces in LP: #1827961

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-29-generic 5.3.0-29.31
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: peder 3620 F.... pulseaudio
 /dev/snd/controlC1: peder 3620 F.... pulseaudio
 /dev/snd/pcmC1D0p: peder 3620 F...m pulseaudio
 /dev/snd/controlC0: peder 3620 F.... pulseaudio
CurrentDesktop: i3
Date: Thu Feb 6 12:11:54 2020
InstallationDate: Installed on 2019-10-31 (98 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 20Q1S6WC00
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-29-generic N/A
 linux-backports-modules-5.3.0-29-generic N/A
 linux-firmware 1.183.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:

dmi.bios.date: 08/13/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET77W (1.55 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q1S6WC00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN2JET77W(1.55):bd08/13/2019:svnLENOVO:pn20Q1S6WC00:pvrThinkPadX390:rvnLENOVO:rn20Q1S6WC00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q1S6WC00
dmi.product.sku: LENOVO_MT_20Q1_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

I don't see anything wrong in the dmesg.

[Kai-Heng Feng (kaihengfeng)]

Maybe test latest mainline kernel and hope for the best:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/

[Peder Stray (pstray)]

I see some of these after the fact:

[ 1830.337382] sd 0:0:0:0: ioctl_internal_command return code = 8070000
[ 1830.337389] sd 0:0:0:0: Sense Key : Hardware Error [current]
[ 1830.337392] sd 0:0:0:0: Add. Sense: No additional sense information
[ 1830.829484] sd 0:0:0:0: ioctl_internal_command return code = 8070000
[ 1830.829491] sd 0:0:0:0: Sense Key : Hardware Error [current]
[ 1830.829494] sd 0:0:0:0: Add. Sense: No additional sense information

[Peder Stray (pstray)]

This i still the case for 5.3.0-46... networking just stops after a while, last i checked (today), it took under 40 minutes before i needed to reboot. Still running 5.3.0-24 where it all worked fine.

[Peder Stray (pstray)]

This time, no messages in dmesg besides some cpu throttling messages

[Peder Stray (pstray)]

Upgraded all firwares (Thunderbolt controller 20.00, System firmware 0.1.65), and to ubuntu 20.04 with the 5.3.0-51-generic kernel. Same problem there, networking through the dock just stops working after a while... this time about 20 minutes after boot.

[Kai-Heng Feng (kaihengfeng)]

Can you please test 5.4 based kernel under Ubuntu 20.04?

[Peder Stray (pstray)]

Yes, wonder why that kernel wasn't installed by the upgrade... up and running for 43 minutes and counting :)

[Peder Stray (pstray)]

Seems to be working... worked for 6.5 hours (until i powered down) after booting into 5.4.0-31-generic yesterday. No crashes yet today (4:20 since boot).

[Kai-Heng Feng (kaihengfeng)]

Great, let's close it.