Fedora 42: driver issues with kernel 6.15 thunderbolt docking station, igb, usb

Ask Fedora
, ,
1

hi,

since kernel 6.15 i’m experiencing igb issues with my thunderbolt 3 dock (caldigit ts3), journalctl is as follows:

kernel: igb 0000:06:00.0 enp6s0: NETDEV WATCHDOG: CPU: 8: transmit queue 3 timed out 5001 ms
kernel: igb 0000:06:00.0 enp6s0: Reset adapter 

# inxi -N
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e
  Device-2: Intel I210 Gigabit Network driver: igb

network connection is not possible, the adapter resets every time.
i’ve downgraded to 6.14.11 currently with no problems.

EDIT:
ok, with the 6.15 kernel it seems that more problems exist, i have these messages while booting and most usb devices on my dock do not work:

kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-4: 5:0: cannot get min/max values for control 2 (id 5)
kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-4: 5:0: cannot get min/max values for control 2 (id 5)
kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-3.1: 2:0: cannot get min/max values for control 2 (id 2)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-3.1: 12:3: cannot get min/max values for control 2 (id 12)
kernel: usb 1-4: 5:0: cannot get min/max values for control 2 (id 5)
kernel: usb 1-4: 5:0: cannot get min/max values for control 2 (id 5)
kernel: usb 1-4: 5:0: cannot get min/max values for control 2 (id 5)
kernel: usb 1-4: 5:0: cannot get min/max values for control 2 (id 5)
kernel: usb 1-4: 5:0: cannot get min/max values for control 2 (id 5)

is there a kernel issue or something i can do?
thanks

3

You can report a bug at

Then you can only wait…

4

i searched the bug tracker and found these 2 issues:

they seem to me kind of related / describing the same problem. so i guess i have to wait…

thank you for your suggestion and reply :slight_smile:

1 Like
5

i just edited my original post, it seems like there are more driver issues with 6.15… maybe somebody else has these problems

6

Please be specific and provide details. In-kernel driver issues will affect multiple distros as they move to 6.15 kernels. By providing examples (a few lines for each) for ALL the error messages, web searches can find this topic and help establish patterns.

7

hello, thank you for your reply. i’m afraid, i cannot give examples for these error messages, because they appear at startup. i just start up with the dock connected.

i then checked my USB Headset (connected to the dock) which is not working. so i assumed it might be related to the startup messages.

8

Without more information we can’t determine if your issue is the same as the one addressed in this topic or make any progress towards a solution. Did you get a bunch of messages like:
cannot get min/max values for control <N>?

Linux usually captures enormous numbers of messages, most routine, some informational. There are many ways to view what is captured. Does the system boot to a GUI environment? Are you stuck without a working monitor? If you can get a text console or terminal in the GUI you should use journalctl (Linux Handbook: journalctl Command) to see if any relevant entries were captured. If you have a monitor that doesn’t require the dock, try booting without the dock and use journalctl --no-hostname --follow to see messages while connecting the dock.

9

Did you get a bunch of messages like:
cannot get min/max values for control <N>?

no, i do not find these messages in my journalctl when connecting after boot (headset works this time).

i have taken a log with journalctl when connecting the dock. everything else on the dock is working, dual monitor, mouse, this time the usb headset worked too. just the network adapter does not connect and resets all the time.

here are some parts of the log:

directly when connecting:

Jul 08 11:38:15 kernel: thunderbolt 0-2: new device found, vendor=0x3d device=0xd
Jul 08 11:38:15 kernel: thunderbolt 0-2: CalDigit, Inc. TS3
Jul 08 11:38:15 boltd[1241]: probing: started [1000]
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] parent is ee263804-a005...
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] connected: connected (/sys/devices/pci0000:00/0000:00:08.3/0000:34:00.5/domain0/0-0/0-2)
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] auto-auth: authmode: enabled, policy: iommu, iommu: yes -> ok
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] auto-auth: security: iommu+user mode, key: no -> ok
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] authorize: authorization prepared for 'user' level
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] udev: device changed: authorizing -> authorizing
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] udev: device changed: authorizing -> authorizing
Jul 08 11:38:15 kernel: pcieport 0000:00:03.1: pciehp: Slot(0): Card present
Jul 08 11:38:15 kernel: pcieport 0000:00:03.1: pciehp: Slot(0): Link Up
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] authorize: finished: ok (status: authorized, flags: 0)
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] auto-auth: authorization successful
Jul 08 11:38:15 boltd[1241]: [d6010000-00a0-TS3                        ] udev: device changed: authorized -> authorized

…

Jul 08 11:38:16 kernel: igb: Intel(R) Gigabit Ethernet Network Driver
Jul 08 11:38:16 kernel: igb: Copyright (c) 2007-2014 Intel Corporation.
Jul 08 11:38:16 kernel: igb 0000:06:00.0: enabling device (0000 -> 0002)
Jul 08 11:38:16 kernel: igb 0000:06:00.0: added PHC on eth0
Jul 08 11:38:16 kernel: igb 0000:06:00.0: Intel(R) Gigabit Ethernet Network Connection
Jul 08 11:38:16 kernel: igb 0000:06:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 64:4b:f0:01:fe:7c
Jul 08 11:38:16 kernel: igb 0000:06:00.0: eth0: PBA No: 000200-000
Jul 08 11:38:16 kernel: igb 0000:06:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
Jul 08 11:38:16 NetworkManager[1348]: <info>  [1751967496.1278] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/10)
Jul 08 11:38:16 kernel: igb 0000:06:00.0 enp6s0: renamed from eth0
Jul 08 11:38:16 NetworkManager[1348]: <info>  [1751967496.7021] device (eth0): interface index 4 renamed iface from 'eth0' to 'enp6s0'
Jul 08 11:38:16 NetworkManager[1348]: <info>  [1751967496.7088] device (enp6s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jul 08 11:38:16 NetworkManager[1348]: <info>  [1751967496.7383] settings: (enp6s0): created default wired connection 'Wired connection 1'

…

Jul 08 11:38:20 kernel: igb 0000:06:00.0 enp6s0: igb: enp6s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5585] device (enp6s0): carrier: link connected
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5591] device (enp6s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5609] policy: auto-activating connection 'Wired connection 1' (1598c713-628a-30cb-92ea-4b0f44673267)
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5612] device (enp6s0): Activation: starting connection 'Wired connection 1' (1598c713-628a-30cb-92ea-4b0f44673267)
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5613] device (enp6s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5616] device (enp6s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jul 08 11:38:20 audit[1242]: NETFILTER_CFG table=firewalld:37 family=1 entries=42 op=nft_register_rule pid=1242 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5736] device (enp6s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jul 08 11:38:20 NetworkManager[1348]: <info>  [1751967500.5751] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds)
Jul 08 11:38:20 avahi-daemon[1108]: Joining mDNS multicast group on interface enp6s0.IPv6 with address fe80::d35c:47dc:bed:f3fd.
Jul 08 11:38:20 avahi-daemon[1108]: New relevant interface enp6s0.IPv6 for mDNS.
Jul 08 11:38:20 avahi-daemon[1108]: Registering new address record for fe80::d35c:47dc:bed:f3fd on enp6s0.*.
Jul 08 11:38:20 ModemManager[1238]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:03.1/0000:04:00.0/0000:05:00.0/0000:06:00.0': not supported by any plugin
Jul 08 11:38:22 boltd[1241]: probing: timeout, done: [2485873] (2000000)
Jul 08 11:38:22 kernel: [drm] DMUB HPD RX IRQ callback: link_index=4
Jul 08 11:38:22 kernel: [drm] DMUB HPD RX IRQ callback: link_index=4
Jul 08 11:38:22 kernel: [drm] DMUB HPD RX IRQ callback: link_index=5
Jul 08 11:38:25 kernel: igb 0000:06:00.0 enp6s0: NETDEV WATCHDOG: CPU: 3: transmit queue 0 timed out 5289 ms
Jul 08 11:38:25 kernel: igb 0000:06:00.0 enp6s0: Reset adapter
Jul 08 11:38:27 abrt-dump-journal-oops[1519]: abrt-dump-journal-oops: Found oopses: 1
Jul 08 11:38:27 abrt-dump-journal-oops[1519]: abrt-dump-journal-oops: Creating problem directories
Jul 08 11:38:28 abrt-dump-journal-oops[1519]: Reported 1 kernel oopses to Abrt
Jul 08 11:38:28 systemd[1]: systemd-localed.service: Deactivated successfully.
Jul 08 11:38:28 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 08 11:38:28 audit: BPF prog-id=60 op=UNLOAD
Jul 08 11:38:28 audit: BPF prog-id=59 op=UNLOAD
Jul 08 11:38:28 audit: BPF prog-id=58 op=UNLOAD
Jul 08 11:38:29 systemd[1]: snapperd.service: Deactivated successfully.
Jul 08 11:38:29 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=snapperd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 08 11:38:29 systemd[1]: snapperd.service: Consumed 315ms CPU time, 100.3M memory peak.
Jul 08 11:38:30 kernel: igb 0000:06:00.0 enp6s0: igb: enp6s0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

and then it seems to repeat.
are there any other infos i could provide? currently it seems like only networking is affected.

10

update: the issue persists on kernel 6.15.5-200.fc42.x86_64

messages in the log when trying to enable adapter via gnome:

Jul 15 13:44:01 kernel: igb 0000:06:00.0 enp6s0: NETDEV WATCHDOG: CPU: 2: transmit queue 1 timed out 5798 ms
Jul 15 13:44:01 kernel: igb 0000:06:00.0 enp6s0: Reset adapter
Jul 15 13:44:02 abrt-dump-journal-oops[1547]: abrt-dump-journal-oops: Found oopses: 1
Jul 15 13:44:02 abrt-dump-journal-oops[1547]: abrt-dump-journal-oops: Creating problem directories
Jul 15 13:44:03 abrt-dump-journal-oops[1547]: Reported 1 kernel oopses to Abrt
11

You might need a firmware update for the dock. I only see updates for macOS and Windows, but fwupd does support some CalDigit devices.

12

thanks for your reply. i already tried that and connected the dock to a macbook. unfortunately for the “TS3” there are no updates, as far as i can see. the “TS3 Plus” has updates, but i dont have problems with that dock.

13

I am experiencing the same issue with my Elgato TB3-dock. It is only wired connection that seem to be malfunctioning. During boot I recieve similar issues regarding invalid MAC address for wired connection (intel driver I210). Everything started with upgrade to kernel 6.15 and I fortunately kept (marked) last working kernel from the 6.14 branch. Running a Dell Latitude 7450 laptop here.

1 Like