Firebox Marvel ports locking up (CORE-E SERIES)
-
Engineer, have you not tried 2.1.5 on the Firebox yet? I've been using that for over a year without any problems 24/7. BSD 10.1/Pfsense 2.2.4 has a bug somewhere for sure using this old hardware. I'm building a new system now so can just retire my Firebox on 2.1.5.
corvey, I'm not using a firebox…just jumped in this thread because it was very similar to my issue. I'm running new hardware (Supermicro X11SBA-LN4F with Intel N3700 board with 4 Intel A210-AT ports). I tried to install 2.1.5 but couldn't get around ROOT MOUNT ERROR no matter what I did. I spent half a day trying to get it to install from both a USB stick and burned CD....no luck.
I might try again later when people aren't in the house using the Internet (they yell within 10 seconds of the watchdog triggering...sigh)
I know, I should have started my own topic (or stayed in the X11SBA-LN4F thread right below this one....just trying to solve both my and Deanot's issue).
-
I have an HP 4 port nic coming, Dual intel chipset. I will build a machine outside of the Firebox, see how it works out, I do hope this is not a driver issue with the build. If it is, I will use an older version and avoid the newer builds until certain the issues are resolved.
A few things I do know.
(1) it is not device dependent.
(2) It started to happen on the 2.2.4 Nano BSD build for myself and the regular 2.2.4 build for Engineer.
(3) Pulling the network cable from the port resets the port and the issue goes away. For a while at least.
(4) Time is not a factor, I have seen my box run anything up to 14 days without issue, then BAM. Or it could happen within minutes, hours or days of being up.
(5) Heavy traffic or minimal traffic has not much affect, for me, I could just log into the GUI and it would trigger it.
(6) Slowing the Nic Speed down, changing settings related to Nic cards had little to no effect. -
I turned off VLAN_HWTCO (ifconfig igb2 -vlanhwtco) and also apinger (WAN PORT MONITORING). Log is down to less than 5% of what it was (things were restarting and checking VERY often. One+ days up with little in the log. Time will tell.
-
Keep us posted, you might drill down into what the actual issue is.
-
Keep us posted, you might drill down into what the actual issue is.
Very sad. LAN port watchdog timeout again. :(
Not sure where I'm going from here…..
-
Hello,
I am affected too! :(
Just a question: I have the LCDProcDev version running on my Firebox. When the lock up happens on your machines is the LCDProc still running? On my machine there is no change on the display.
So I thougt it has completely chrashed and I switched it off andf on again.Matthias
-
I run it too, it continues to function like nothing is wrong.
-
I have a X750e with deactivated MSK intefaces.
I will give it a try to use them instead of the sk interface I currently use…. -
2.2.5 is out, maybe they fixed this bug.
-
I don't think 2.2.5 is a nano build is it?
-
No you're right, it is a nano build. I might try it out later, just to see if it is better or not.
-
2.2.5 Nano installed, I had to reset the ports about 18 times before I could get it on. But it is on and running, and I am testing and abusing the ports to see if I can get it to lock up again. At this time, I do believe it will do the same…..
-
That was short lived, locked up within minutes of posting this. Oh well, time to ditch this brick and find something more reliable or go back to 2.1x
-
That sucks, thanks for trying 2.2.5 for us, deanot. I will be retiring my Firebox on 2.1.5 and use it as a solid backup router.
I'm still waiting on my 1265Lv2 Xeon CPU to arrive from Fleabay. I will be going ESXI this time around to install Pfsense on. Hopefully it works.
-
I fired the box up again this morning, this time I uninstalled Snort, so far it has been up and running solid for the past few hours. I am still expecting it to lock up on me, just have to wait for when it happens.
The only extension I am running right now, is LCDproc-Dev. Nothing more, nothing less.
-
I did receive my HP 4 port intel nic card, I should be building up a new PFSense system sometime today, I am going to load a full install of the latest build on it and see what happens. I am unsure if I want to restore my settings or start out completely fresh and hope for the best.
Being unsure of what is causing this, I feel the best approach would be to do everything from fresh. For all I know, it could be my config that is doing it, it could be from a previous install doing it. All I know, when I was on 2.1.x, it worked just fine.
Without much information from devs, I have no idea if drivers got updated/changed or what could be causing this. I do know it is a known issue for some network cards, but nothing was mentioned about the Marvel nics, and this does seem a little more wide spread than just my system doing this as of right now. It is apparent, this is not just firebox related anymore.
-
Just a quick update, 25 hours and still going. Not one reboot in this time, not to say it is stable, but it could go at any moment.
I will continue to update…
Only thing I did was remove snort, I can't believe that would be the fix, we shall see..
-
3 days, 12 hours and still chugging along.
-
Maybe the hardware is just finally giving up the ghost?
https://forum.pfsense.org/index.php?topic=101920.0 -
Maybe the hardware is just finally giving up the ghost?
https://forum.pfsense.org/index.php?topic=101920.0I don't believe this is the case, the logs show nothing like that and this has only started since going onto 2.2.3. It is also across multiple systems, mine being the box listed below, the other on a PC system with an intel chipset card. Mine is still up and running and appears to be stable, but saying that, it has gone as long as 15 days if I remember correctly.
Thanks for the link anyway.