Created attachment 763960 [details] dmesg excerpt This kernel started crashing (temporarily) my NIC in one of my systems, relevant messages: [260309.329734] tg3 0000:02:00.0 enp2s0: transmit timed out, resetting [260311.035584] tg3 0000:02:00.0 enp2s0: 0: Host status block [00000001:00000078:(0000:01b8:0000):(01b8:0025)] [260311.035592] tg3 0000:02:00.0 enp2s0: 0: NAPI info [0000002b:0000002b:(0025:0003:01ff):0169:(0031:0000:0000:0000)] [260311.138113] tg3 0000:02:00.0: tg3_stop_block timed out, ofs=1400 enable_bit=2 [260311.295146] tg3 0000:02:00.0 enp2s0: Link is down [260312.078409] br0: port 1(enp2s0) entered disabled state [260314.529485] tg3 0000:02:00.0 enp2s0: Link is up at 1000 Mbps, full duplex [260314.529497] tg3 0000:02:00.0 enp2s0: Flow control is on for TX and on for RX [260314.529553] br0: port 1(enp2s0) entered blocking state [260314.529560] br0: port 1(enp2s0) entered forwarding state (full dmesg excerpt attached) tg3 is a module, firmware is in place, going back to kernel 5.10.76 removes the issue. emerge --info and lspci output attached.
Created attachment 763961 [details] lspci -k for tg3
Created attachment 763962 [details] emerge --info
I should have added that there are old reports online that prompt for a kernel update (https://access.redhat.com/solutions/69382) and others that prompt for the use of latest firmware (https://support.exinda.gfi.com/hc/en-us/articles/360015182039), so I'm wondering if this is a regression.
Apologies, kernel version was wrong as it was a slightly newer one that showed this problem. Sadly, however, .11 had other problems that I'm dealing with (https://forums.gentoo.org/viewtopic-p-8690041.html) and am collecting some evidence for to open a different bug.
(In reply to Gabriel from comment #4) > Apologies, kernel version was wrong as it was a slightly newer one that > showed this problem. > Sadly, however, .11 had other problems that I'm dealing with > (https://forums.gentoo.org/viewtopic-p-8690041.html) and am collecting some > evidence for to open a different bug. please test with the latest 5.15.X kernel which is 5.15.18 as of this writing
OK, reporting back with new kernel (.19), updated linux-firmware (didn't run a diff, so not sure if this had anything to do) and updated microcode (really, the CPU is so old that I doubt this had anything to do with the problem). The NIC is now working OK, so I think this bug can be closed. The side problem I had (https://forums.gentoo.org/viewtopic-p-8690041.html) appears to also have been fixed.
