X520 errors in 2.6 and 22.01?
-
So you definitely didn't see those errors in 2.5.2?
41177 is very different to 3170, what makes you think they are related?
Do you have checksum hardware off-loading enabled?
Steve
-
The image is after a reboot. Never an error with the 2.5.2 . The "Hardware Checksum Offloading" is enable by default.
-
Ok, so before that the checksum error count matched?
Try disabling checksum off-loading.
Steve
-
Yes, the value is the same. I tried to disable "Hardware Checksum Offloading" but it didn't work.
thank you for the support
-
Like it didn't disable it or just didn't change the error count?
The errors could be genuine of course. Perhaps the updated driver is now reflecting the correct values.
Steve
-
With a VM i compiled the latest driver ("if_ix.ko" ver3.3.29) for freebsd 12.3 and I put it in the pfsense, but I got nothing!
Any idea?
-
I'm not sure how helpful this will be, but it looks like there were several updates made to the Intel drivers in FreeBSD 12.3 (look under Drives):
https://www.freebsd.org/releases/12.3R/relnotes/
The issue might be upstream from pfSense.
-
@stephenw10 said in X520 errors in 2.6 and 22.01?:
Like it didn't disable it or just didn't change the error count?
^?
Does it show your new driver was correctly loaded at boot? If not does it show an error?
-
The driver is loaded correctly. I think the driver is not the real problem. If it can help, my switch is a hp/aruba JL261A. In the next few days I will try to install some fiber optic transceivers. -
@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 ...
