This type of issue with the Intel e1000e driver seems to have been an issue since at least 2013.
From my internet searching I have found people complaining about this happening from 2013 all the way up to 2024 and yours now makes 2025.
It looks like Intel has no plans to fix it and from the searching the solution that kept being used and said to fix the problem is to turn off gso, gro & tso in the nic. These are various off loading functions and I would expect that removing these would affect the performance to some extent.
If you want to do that you would need to run the command
ethtool -K red0 gso off gro off tso off
Which is what the users in the various web sites I found did.
However I suspect that when you reboot they would get turned on again so you would need to add that command into the rc.local file to get run during the boot cycle. https://www.ipfire.org/docs/pkgs/rc-local
As to why it only started now, there was a kernel update in CU190 so either there was a change to the e1000e driver or something else changed in the kernel that causes the e1000e driver to hang.
The other thing that worked for some users suffering from this problem was a change of NIC but that is only feasible if the NIC is an add-in card.
Grimm did add the missing intel drivers, but I do recall him mentioning he removed the reinitialise routine on network drivers so they can remain in sync with power management. Of course in our application, we should have them in an ‘always on’ state instead. So power management will be something to look at if any thing operates or behaves differently.
I try to disable this settings, but dont want to risk. Intel NIC is onboard on my system. I change it with one external Realtek… but from all years i have the system there is no one error on Intel NIC. This is for the first time after yersterday’s update to core 190. Maybe will be good if the part of kernel related for Intel e1000e driver is roll back
Its not really a change in the driver, but the system. But to let you know, I loaded 190 from a burned iso cdrom because updating caused my 4 port intel card to act up. So their update must be missing something that they should shutdown first before applying it or something like that.
