Firebox Marvel ports locking up (CORE-E SERIES)
-
That is for the firebox core series not the core e series which have Marvel based nics
-
That is for the firebox core series not the core e series which have Marvel based nics
You are correct, my mistake but very similar to our problem.
-
How often are you seeing this? Do you mainly see it with heavy traffic? Just trying to compare and to see if there is something you're running that might be contributing to the issue. Are you running any add-ons?
-
I was only running LADVD, LCDPRocDEV and was still having the problem. I could only get around a hour or so out of the box before it would lock up. I thought it was Snot that was contributing to the issue but I had it disabled and still had the problem. The only thing I can think of is the config I restored came from a completely different box so I have now wiped my Card and did a re-install with an upgrade to the latest bios 8.1 we will see if that helps. I am currently running a base config that I did by hand with only LCDProc Dev installed. I will see if it lasts the night and let you know. I also had IPV6 with Prefix Delegation running but I have that turned of on my new install now. I will post back in the morning on how things are going.
Update everything was still running this morning Thursday after I woke up so things are going ok so far. I am going to let it run the rest of the day while I am at work. If it is still stable then I will start adding things back on one at a time starting with my IPV6 and so on.
-
I am still getting this lockup issue, same as yours, if I remove the lan cable and plug it back in, the port must reset and it works again. So it seeing the state as up to down and back to up, must reset something in a sense.
This is getting kinda old, I am considering pitching this Firebox as the hardware is not very reliable in this new build. When I say hardware, it has to be a driver issue for the Marvel Network ports.
-
I am still getting this lockup issue, same as yours, if I remove the lan cable and plug it back in, the port must reset and it works again. So it seeing the state as up to down and back to up, must reset something in a sense.
This is getting kinda old, I am considering pitching this Firebox as the hardware is not very reliable in this new build. When I say hardware, it has to be a driver issue for the Marvel Network ports.
Yep. Glad I'm not the only one seeing this issue. My x750e does the same thing with a fresh 2.2.4. install. The disconnects in 2.2.4 with Firebox are unacceptable. v2.1.5 is solid and that's what I reverted back to from my backup. I'm ordering pieces and parts to build a new faster system for PFsense and then am going to test it out throughly before actually making the switch to new hardware in the network.
-
Wish I could find a way to roll back, I upgraded from the GUI, so it has been overwritten. I find, the more time I spend in the GUI, the more often it will lock the port up. I also find, using IE in the GUI is less harsh than running Chrome to access it.
-
Last night it was lock up after lock up, something I have done to the box is to drop the LAN port speeds to 100base Full Duplex. I do not use the ports for subnet routing, both ports are on the same subnet, one is for access in case of a lock out (got to love headless boxes).
Since I have done this, the throughput seems better, the box seems to be more responsive and it has not locked out…. YET.
I shall update as to how this box is now working out.
-
one is for access in case of a lock out (got to love headless boxes).
At the IPMI port if one is there it would be ok, but if not using the IPMI port for this action
you could be creating a network loop! And then this could be the problem for locking out!!! -
Slowing my port speed down seems to have worked.
-
I'm not using a Firebox but I'm having similar lockups….can't access anything on LAN (and Internet stops) but console still working fine (monitored through IPMI port). It was suggested in other threads around the web to not set "Autodetect" for the port speed. Have you by chance set it to 1000T full duplex instead of Autodetect to see if that helps? (if you have done so, my apologies...just curious).
I'm going to follow this thread as it seems very much like what's happening to my SuperMicro N3700 setup. If my system locks up again, I'm going to do the same (unplug the LAN and replug to see if it comes back to life. I really hate to lower my port speed down - even though it wouldn't effect my network as my ISP is well below 100Meg).
Good luck.
-
Yeah, I set my ports at 100 base and full duplex. I think the speed of the ports was causing the issue. It has been up solid for over 24 hours now.
-
Yeah, I set my ports at 100 base and full duplex. I think the speed of the ports was causing the issue. It has been up solid for over 24 hours now.
Did you have it set to 1000T full duplex before that or "Auto Detect"?
-
Sorry, it was on auto detect from install. Pfsense even says it should be set to auto detect.
-
Sorry, it was on auto detect from install. Pfsense even says it should be set to auto detect.
I had read from a few places that setting to auto detect would cause issues similar to yours (and mine) and that setting it to a fixed speed would fix it. I set mine to 1000T Full Duplex yesterday morning in hopes it would correct the issue. Now just wait and see.
-
Yeah, mine seems stable, I don't really need 1000Base on mine, it handles internet traffic only. Seeing as the ports on the modem are 100Mbps max, I see no reason to crank it higher at this time.
-
I have mine set at auto negotiate and it seems to be stable though I still get the random lockup but is now going days between lockups. The other day I tried to install Snort back on my box and it locked up within an hour of the install. I now have snot off for the last 4-5 days and it only locked up on Saturday once and that was with snort removed from the box. One thing I did do was to increase the size of the /tmp file system which resides in ram. I have pleanty of ram to spare as I am running 2gb of ram in my box. I bumped it up to 128MB just as a test and knock on wood has been running since Saturday evening eastern time.
-
My box has been up and running without issue now for 2 days and 21 hours, Snort has been back on it over 2 days now. Still no issues… Fingers crossed.
-
Mine locked up around 30 minutes ago. I went to the console and it was working. Before I could go downstairs to unplug and replug the LAN, it came up with this message (added attachment). After that, Internet would partially work. Had to go in and disable IPV6 to get it all working. Note, the first time it locked up (last week), IPV6 was disabled so I'm not sure it had anything to do with IPV6. The watchdog seems to be the key here. Any thoughts?
-
I am going to quote this again, i know we are not talking about realtec cards, but the symptoms are almost identical.
Known Issues
The Realtek NICs in this box are known to suffer a lock-up condition under certain circumstances. Despite repeated efforts it has not been possible to either cure the problem or ascertain exactly what triggers it. When the problem is triggered the system log will show watchdog timeout and refer to the interface causing it. Fortunately this doesn't affect all users and even then only under some circumstances.
It would seem to be related to packet fragmentation and hardware off loading. Some users have reportedly solved the problem by disabling all hardware offloading and/or using a better switch that can reassemble packets correctly.