msk0 watchdog timeout

Started by smajor, June 21, 2015, 06:41:32 PM

Previous topic - Next topic
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.

Hi there,

thanks for the link and the thorough description of the issue. I have added the alleged fix and built a custom kernel for you to try out:

# opnsense-update -kr 15.1.12_msk && reboot

(I am guessing you are using amd64, if not this won't work until you let me know.)

If you let us know if this works for you we can include the fix for 15.7 and also try to push it to FreeBSD.


Cheers,
Franco

Hello,

Thank you for the quick reply - just fantastic!

I don't believe that will work for me, but correct me if I'm wrong. The older box is 32-bit only (core2duo that is 64-bit capable, but sadly no 64-bit BIOS support) so i386 is the version of OPNsense I've installed.

Thank you again.

Ok, will provide a i386 kernel for testing tomorrow morning. :)

Kernel for i386 is up, the command above remains the same.

Thanks! Installed.

I was seeing the error every few hours under load, so I should know quickly if it is better. I'll probably let it go for a couple of days (unless it happens again) before reporting back.

Thank you again.

Well, unfortunately, that didn't fix it.

I'm going to run off a USB->Ethernet adapter instead of the built-in NIC for awhile to be sure that the problem is not something about my system (hardware).

If I get that error with the adapter, maybe my older computer I'm using this for is having an issue of some sort.

Sorry about that. The driver seems to be unmaintained so there's no more we can do about it. Thanks for testing though.

No worries at all, it's been working great with a USB adapter.  I'll probably update the hardware in a few months anyhow. Thanks!