System freeze with 2.1-RELEASE
-
I have the same issue since i upgraded to 2.1 RELEASE. I've been using the 2.1 snapshots before that and everything was perfectly fine. Can someone refer me to a download page for the old 2.1 snapshots, i can't find them anywhere on the site?
Last night i downgraded to
2.1-BETA1 (i386)
built on Mon Apr 29 20:54:19 EDT 2013
FreeBSD 8.3-RELEASE-p8because it was the only thing i have on cd and i know it doesn't freeze.
-
I've been having the same issues where the box will just lockup and become unresponsive to keyboard commands, using bge interface with vlans for both lan and wan connects along with ipv6 connectivity from he.net and igmproxy for iptv service in the house.
Was working great on the pfsense-2.1 snapshots before the release edition came out so not sure what would be causing the issues but I hope it gets resolved soon as this just is to unstable to continue using like this even in a home enviroment.
I however have just switched from i386 to amd64 arch so will be interested to see if it resolves it self now after a fresh install and config restore, uptime usally lasts for 5 days tops and they dies.
I was remote syslog'n to try and catch any errors before the freeze but found nothing in the logs to pinpoint anything down.
Thanks
-
What does your memory usage look like? Some people have been seeing a memory leak that might exhibit like this.
Do you have a console connected to the box? Are you seeing a kernel panic? Anything else on the console that doesn't make it into the logs?Steve
-
No memory leak from what I can see and console looks just fine so not sure what it is that causes this freeze but it happened again so I had to hard reset the box and then like less then a hour went by and it froze up again so it seems like its getting worse.
What snapshot from the 2.1 branch does not have this freezing in it cause I would love to switch back to it so I don't have to have all this downtime.
-
I have no idea, all my 2.1 boxes are running fine.
Are you running 64bit? Perhaps try 32bit. Edit: forget that I see you already tried it.Steve
-
Yeah I had 32bit running then did a fresh install of 64bit and both arch's freeze up.
Now I do note that I'm running igmproxy for IPTV such like another fellow in this thread so I wonder if multicasting is related to this or perhaps upnp.
Being a technical orientated guy such as my self I hate to just give up and rollback to snapshots but this really is just not stable enough for even home usage.
Hopefully the powers that be see this as a problem that needs swift action against it and release a fix sooner then later.
-
Here's one more odd observation I should have noted … I run FreePBX for the phone system in the house and it would appear that most of the freezing happens when using the phone.
This last freeze right after I reset the box I used the phone and then it froze again in under a hour so not sure how it relates but just thought I'd throw that out there.
Fairly sure pbx uses UDP so ...
-
Ok so I've just gitsync'd to the latest RELENG_2_1 branch which from what I read contains the updates and fixes that should be present in the 2.1.1 release whenever that happens so hoping this will resolve my issues but will see how it goes.
For now I'm running top in a terminal and will be able to figure out if this is memory related such as you say or not for sure.
Thanks
-
Froze again today well I was using my sip phone in the house that routes through my pfSense box so thats the 5th time so far that it's froze well using SIP protocol.
-
Are you using multicast at all?
What NICs are you using? What sort of internet connection do you have?Steve
-
Yes I'm using multicast (iptv and upnp).
NIC is bge0: <broadcom gigabit="" ethernet="" controller,="" asic="" rev.="" 0x004001="">.
25Mbit down and 6.5Mbit up ADSL.This is all on vlans as well.</broadcom>
-
I attempted to upgrade to 2.1 last week and also ran into random system hangs. Ctrl-T at the console would show different processes usually each hang.
Like others have reported, the system didn't panic. It just became slow as nothing would work due to timeouts.
I'm running multiple supermicro dual processor XD7CU boards with 8GB of RAM, and nothing special multi-cast wise. The systems hang started before I could even configure the box. The hang would some times happen during boot as well. I was running with the Live CD and a usb pendrive for the config file.
I did not attempt to turn of VTx or multi-cores since I didn't see that hint until recently. I downgraded back to 2.0.3 and all is fine.
-
I attempted to upgrade to 2.1 last week and also ran into random system hangs. Ctrl-T at the console would show different processes usually each hang.
Like others have reported, the system didn't panic. It just became slow as nothing would work due to timeouts.
I'm running multiple supermicro dual processor XD7CU boards with 8GB of RAM, and nothing special multi-cast wise. The systems hang started before I could even configure the box. The hang would some times happen during boot as well. I was running with the Live CD and a usb pendrive for the config file.
I did not attempt to turn of VTx or multi-cores since I didn't see that hint until recently. I downgraded back to 2.0.3 and all is fine.
Just an FYI - turning off VTx and multi-cores did solve the problem for me.
-
Updating to the most recent Github 2.1 release branch has solved the problems for me all together.