X520 errors in 2.6 and 22.01?
-
Why? The errors could be on one NIC only. You just didn't see them reported in 2.5.2.
-
Just curious if anyone ever found anything that might explain the source of these errors?
-
Seeing something similar I think.
On my LAN interface (multiple VLANs via a 10G Intel/ix Interface) i get exactly 2 IN errors every 20 seconds.
It's 2 errors. It's every 20 seconds. Like clockwork. I can run gigabits of traffic through the firewall and it only ever increases by 2 input errors, only every 20 seconds.
What on earth could this be? Something on my LAN sending dodgy frames? Why every 20 seconds?
Is there anyway to get a pcap of the dropped / error frames?
-
Hmm, that's interesting.
You could probably catpure that by using a mirror port on the switch to reflect whatever it's sending.
Steve
-
@stephenw10 Yes, setting up to do that now. I assume it's my Ubiquiti switch. Cheap 10G switch = cheap 10G switch problems, I guess.
-
@simplepanda Curious what you see. I have a similar situation just not with fixed pattern. Mine is just a slow increment of ~50 errors every 24hrs on both WAN interfaces. I've got a USW-Flex-XG between the WAN NICs and the respective modems (AT&T and Spectrum).
-
@brachy33 said in X520 errors in 2.6 and 22.01?:
https://www.intel.com/content/www/us/en/download/19174/disabling-tcp-ipv6-checksum-offload-capability-with-intel-1-10-gbe-controllers.html
Any luck, with those in/out errors
-
Hate to be the latest "me too" but ..
Intel X550-T2 getting errors on both interfaces. ix1 which is connected to 10Gb port on my Aruba switch, there are no errors showing on the Aruba. If its as stephenw10 explained and just more counters being aggregated thats annoying.
dev.ix.0.mac_stats.checksum_errs: 50 dev.ix.0.mac_stats.rx_errs: 50 dev.ix.1.mac_stats.rec_len_errs: 313 dev.ix.1.mac_stats.rx_errs: 313ix0: <Intel(R) X550-T2> mem 0xf0600000-0xf07fffff,0xf0804000-0xf0807fff irq 25 at device 0.0 on pci1 ix0: Using 2048 TX descriptors and 2048 RX descriptors ix0: Using 4 RX queues 4 TX queues ix0: Using MSI-X interrupts with 5 vectors ix0: allocated for 4 queues ix0: allocated for 4 rx queues ix0: Ethernet address: ix0: PCI Express Bus: Speed 8.0GT/s Width x4 ix0: eTrack 0x80000492 PHY FW V523 ix0: netmap queues/slots: TX 4/2048, RX 4/2048 ix1: <Intel(R) X550-T2> mem 0xf0400000-0xf05fffff,0xf0800000-0xf0803fff irq 24 at device 0.1 on pci1 ix1: Using 2048 TX descriptors and 2048 RX descriptors ix1: Using 4 RX queues 4 TX queues ix1: Using MSI-X interrupts with 5 vectors ix1: allocated for 4 queues ix1: allocated for 4 rx queues ix1: Ethernet address: ix1: PCI Express Bus: Speed 8.0GT/s Width x4 ix1: eTrack 0x80000492 PHY FW V523 ix1: netmap queues/slots: TX 4/2048, RX 4/2048Also, hoping for the day when my nic speed is correctly reported too. (this is a 2.5Gbps link to cable modem)
media: Ethernet autoselect (Unknown <rxpause,txpause>) -
Those are present for X550 in 2.7:
https://github.com/pfsense/FreeBSD-src/commit/d381c807510de2ebb453a563540bd17e344a2aabSteve
-
@stephenw10 Thank you!
-
I was not able to track down and prevent IN errors with the X550-T2 (WAN1) and my MetroNet GPON regardless of firmware, settings, etc. So, as a test I bought a Chelsio T520-BT, flashed it to the latest firmware/ROM and reinstalled pfSense+. Have not had a single error (IN or OUT) since making that swap. To be fair, the Chelsio could also be seeing errors and the latest drivers, etc are just not 'showing' those errors within pfSense.
On the flip side, my Intel x710-T2 (LAN) connected via 10G Twinax to my Juniper 2300 started getting IN errors, albeit very slowly so. I would get several 100Gb of data through the network and then all of a sudden 3 errors would show IN, than 12, than 30. The errors ALWAYS increase in increments of 3. Now, these errors do not seem to correlate to the number of interrupts on this connection which do increase steadily AND the overall performance of the network has been rock-solid!
In speaking with the Netgate support team, it might be fruitless and an overall 'red herring' to go tracing down what is causing these LAN IN errors, especially when everything is working as it should.
But call me an OCD freak...I just don't like when there are network errors and I do not know where they're originating from.
-
three days post-2.6 > 2.7 update and have not seen any more of these errors, in nor out.
