I’d check under BIOS to see if there’s a setting to handle wifi and Ethernet activations. On my Dell 5591, there’s a setting to automatically disable wifi if Ethernet is plugged in, and I’m just assuming that wouldn’t work anywhere near ideally from within operating systems and never tried it
I’d also make sure your BIOS is up-to-date. I’ve also heard some Intel Ethernet adapters around the I219 model (maybe I211?) had firmware updates available in other communities that fixed issues.
Looking at that at little closer, it sounds like native_queued_spin_lock_slowpath means that communications with the CPU wasn’t fast enough (deadline scheduling?) One idea could be to make sure the drive is using another scheduler or none (not sure how to do it offhand but NVMe defaults to none)
I don’t know what my revision is, but I have that exact Ethernet (I219-LM) on my laptop. I can try messing with it later to see if I experience anything.
I don’t imagine it’s something specific to Fedora, but on openSUSE TW with kernel 6.8.9-1, hotplugging my Ethernet works fine without any errors in dmesg. I have Intel Corporation Ethernet Connection (7) I219-LM (rev 10)
I see on a Windows driver thread that there’s apparently different drivers for I219 based on the revision. I have rev 10 and apparently use a shared driver between I217/I218/I219 models. Interestingly I see a lot of rev 10 stuff in my lspci and wonder if it’s a chipset thing (I have Coffee Lake).
rev 18+ has a different driver, and yours being 21 might imply some notable difference.
Laptop vendors often try to be “helpful” with switching between wired and WiFi network, particularly with the current emphasis on minimizing power consumption and prolonging runtime on battery. It is not unusual to have issues with some use cases – maybe they only test disabling wired connections when undocking. Sometimes there are workarounds (e.g., manually switch to wifi before disconnecting ethernet cable).
Do you boot more than one OS? Many systems enable some basic networking at boot to support PXE (Preboot eXecution Environment). There can be conflicts due to differences in firmware support between PXE, Wiindows, and Linux. Intel usually fixes those with firmware updates (and corresponding linux module changes), but vendors often add their own tweaks to firmware so you need to get updates from Lenovo as well as Fedora. When reporting issues it is best to fully update Fedora packages and also vendor firmware (e.g., with fwupdtool) so you aren’t wasting time on solved issues.
The problem is indeed related to the Ethernet network card e1000 (00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (10) I219-LM). The system freezes only when I disconnect and reconnect the UTP cable.
I disabled Wi-Fi through the graphical interface and left only Ethernet enabled.
I also disabled the simultaneous operation of Wi-Fi and Ethernet in the BIOS. Now, when I connect to Wi-Fi, it is automatically turned off.
I hope that a new kernel or firmware update will include a fix for this issue.
Thank you, @filippo2 Waiting eagerly. To avoid worsening or creating a problem, I will only use Wi-Fi and not install or change anything until the new kernel is available.
Once again, “Solved” isn’t appropriate until the fix arrives, but it could help others with the same issue to have a “waiting for upstream patch” status.
The latest update I received fixed the problem. In this update, the Linux kernel 6.8.10-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 17 21:20:54 UTC 2024 was installed.
Now everything is working fine, even with both interfaces connected at the same time. I have disconnected and reconnected the UTP cable without any freezes so far.
