76
15.1 Legacy Series / msk0 watchdog timeout
« on: June 21, 2015, 06:41:32 pm »
I'm fairly positive this is a FreeBSD bug, but thought I'd post here in case 1) someone has a workaround or 2) it isn't a FreeBSD bug.
I just installed OPNsense on an older PC using the built-in NIC (Marvel Yukon) and a USB adapter. This is really just for my home with a few users and it gets my WiFi router out of NAT/Gateway duty and into infrastructure mode. So, not a lot of horsepower needed and there is a definite speed improvement and a lot more options!
Everything worked fantastic for about 12 hours, then the console showed:
msk0 watchdog timeout
prefetch unit stuck
initialization failed no memory for Rx buffers
msk0 is my LAN and obviously everything went dead until a reboot.
Again, I'm fairly positive this is a FreeBSD issue based a regression bug here in the 10.x series (there are also 2 other related reports that are in-progress:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186872
My next step, pending other hints here, is to go with another USB Ethernet dongle to see if the error pops up again with a different interface. The older PC I'm using is a small form factor with no PCI slots, hence the USB approach.
I just installed OPNsense on an older PC using the built-in NIC (Marvel Yukon) and a USB adapter. This is really just for my home with a few users and it gets my WiFi router out of NAT/Gateway duty and into infrastructure mode. So, not a lot of horsepower needed and there is a definite speed improvement and a lot more options!
Everything worked fantastic for about 12 hours, then the console showed:
msk0 watchdog timeout
prefetch unit stuck
initialization failed no memory for Rx buffers
msk0 is my LAN and obviously everything went dead until a reboot.
Again, I'm fairly positive this is a FreeBSD issue based a regression bug here in the 10.x series (there are also 2 other related reports that are in-progress:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186872
My next step, pending other hints here, is to go with another USB Ethernet dongle to see if the error pops up again with a different interface. The older PC I'm using is a small form factor with no PCI slots, hence the USB approach.