Traffic stops
-
Unlikely if it's a driver issue. There doesn't seem to have been much work on the et(4) driver since 8.3 was released (2 years ago):
http://svnweb.freebsd.org/base/head/sys/dev/et/if_et.c?view=log
Nothing that looks like it might fix the issue you're having.
Though some of it was sponsored by Netflix so if they're using them you can bet there's no ongoing issues when combined with whatever hardware they're using.When does that DMA error appear?
Steve
-
It appears when pushing under load.
-
Hmm, so no errors at boot then?
Steve
-
No nothing at boot and if there is no load it runs for days. As soon as you push 20Mb or so it goes, so when I say load more then tick over.
-
You could try booting 'verbose' to see if any more clues are given.
It looks like you've already tried evrything I might suggest. :-\Steve
-
Bummer. Guess only thing left is hack the driver :(
-
Since you first asked about this it looks like some dma related fixes have gone into the driver. Probably worth trying though it might only compile against FreeBSD 10.
Steve
-
sweet so we should be good on v2.2
-
Maybe. 2.2 is tracking 10-stable (or was until recently at least) so any bug fixes should be included. Only testing will tell if they address your issue though. ;)
Steve
-
Thanks will update
-
Unfortunately it doesn't look like the patch made it into 10.1, and hence pfSense 2.2. In fact it's not in 10-stable either only in head:
https://svnweb.freebsd.org/base/head/sys/dev/et/if_et.c?view=logYou might have to compile it yourself if you want to try it.
Steve
-
Your right because after testing I didn't have any joys. I am tempted to move it to ESXi anyway which would solve this. A 1GHz via just isn't cutting it anymore now I am running squid and dansgardian.