X520 errors in 2.6 and 22.01?
-
@cescofs said in X520 errors in 2.6 and 22.01?:
I tried to disable "Hardware Checksum Offloading" but it didn't work.
It didn't get disabled or it didn't affect the error count?
-
@stephenw10 Can't speak for @cescofs but all that stuff is disabled on my end:
My error count is relatively small at 1105 with 5 days of uptime and passing through 464GiB of data but it's still higher than the 0 on 2.5.2
-
Mmm, that's a very small number really though. That would not concern me.
Is that still rising? That could all have been when the interface came up for example.Steve
-
@stephenw10
After disabling it, the errors were still there.
Since there are no errors in the output, the drivers should be excluded as a cause. -
@stephenw10 right after booting i had 83 errors. The current count grew a little every day for the last 5 days.
-
@tom-ato
it's the same for me -
I found this ....
link text -
Do you actually see the new driver loaded though:
[22.01-RELEASE][admin@6100-2.stevew.lan]/root: sysctl dev.ix.0.iflib.driver_version dev.ix.0.iflib.driver_version: 4.0.1-k -
no. to find a solution I downloaded the latest version from the intel site for freebsd -
Ok, so it did load and you are still seeing the errors reported by the latest Intel driver.
So maybe that is the correct count and in fact the driver in 2.5.2 was misreporting them.
Steve
-
@stephenw10
it's hard to admit ... -
@stephenw10
do you have any idea how to solve? it's very strange only "errors in" -
@stephenw10 That is a very real possibility. I'm fine with that answer if it is indeed what is happening.
-
@cescofs said in X520 errors in 2.6 and 22.01?:
@stephenw10
it's hard to admit ...pfSense does nothing with the MAC stats, the driver updates them directly.
You could try the alternative driver in 2.5.2.Steve
-
Something must have happened with 2.6. Anyway, I connected the pfsense directly to my pc and.....zero errors!!!!
-
Ah, interesting. So before it was via a switch? I wonder what's different there then. Something enabled on that port? Flowcontrol mismatch maybe?
-
@stephenw10 That's an interesting data point. My pfSense box is connected to an Aruba S2500 and @cescofs is using an Aruba JL261A. Could very well be some weirdness with link negotiation?
-
These are packets from the switch to the lan interface of pfsense. So there are no logs errors about them on the switch.
The only thing we know is that the lan interface has problems for a few of them..... -
@tom-ato
Did you find any solution? -
@cescofs I have not. Checked my port settings on the switch side; flow control is disabled and the interfaces properly auto-negotiated. I can't really remove the switch from the equation since it's a core part of my home network. I haven't tried changing the driver but may do so if the total number of errors goes to an uncomfortable number, currently it's sitting at 1425 which is relatively low.
