Latest kernel makes usb 4 run as 3.0

[Robert Neve]

When my kernel was updated from 6.5.0-35-generic to 6.5.0-41-generic my monitors connected via a thunderbolt 3 dock stopped working. It seemed I did not have the bandwidth anymore. The logs showed I only had v3.0 bandwidth despite it being a v4.0 port. When I went back to 6.5.0-35-generic it worked again. It also worked when I switched to 6.5.0-060500-generic
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: zorin:GNOME
DistroRelease: Zorin OS 17
InstallationDate: Installed on 2024-04-21 (61 days ago)
InstallationMedia: Zorin-OS 17.1 Core 64bit
MachineType: Framework Laptop 16 (AMD Ryzen 7040 Series)
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-41-generic root=/dev/mapper/vgzorin-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.5.0-41.41~22.04.2-generic 6.5.13
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-41-generic N/A
 linux-backports-modules-6.5.0-41-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.31
Tags: jammy wayland-session
Uname: Linux 6.5.0-41-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/27/2024
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMZCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRAGAACPA740940011
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.03:bd03/27/2024:br3.3:svnFramework:pnLaptop16(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMZCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRAGAACP07:
dmi.product.family: 16in Laptop
dmi.product.name: Laptop 16 (AMD Ryzen 7040 Series)
dmi.product.sku: FRAGAACP07
dmi.product.version: A7
dmi.sys.vendor: Framework

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

apport information

[Robert Neve (robertneve)]

I forgot to add I am using a framework 16 with a Ryzen 7 7840HS.

I created a request for help on the framework forum and another person had the same issue.

https://community.frame.work/t/linux-suddenly-lost-my-monitors-on-my-dock/53291/10

[Mario Limonciello (superm1)]

I read on that link that mainline 6.9.3 is fine. So there is some bad backport.

Can you handle building a kernel? If so; it would probably be best to find the cause by bisecting [1].

You would clone the Ubuntu kernel tree [2] that has these tags and use them for your start and end.
Ubuntu-6.5.0-35.35
Ubuntu-6.5.0-41.41

[1] https://www.kernel.org/doc/html/latest/admin-guide/bug-bisect.html
[2] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/mantic

[Matthew Ruffell (mruffell)]

Hi Robert,

Come talk on bug 2070020 and let's try figure this out.

Thanks,
Matthew