System freeze with 2.1-RELEASE
-
Hello guys,
I am experiencing some hard locks with 2.1-RELEASE. After some time the pfSense machine hangs requiring a press of reset button. No crash dumps, no logs, no kernel panics, no info at all.
I made a through memory test, nothing was found. I formatted HD and made a clean 2.1-RELEASE install. The box ran a day or so, then hanged needing to reset by button.
I went back to 2.1-RC2, the problem was gone. Then I upgraded to 2.1-RELEASE, the problem came back.
My machine is a old AMD Duron 1GHz, with 512MB of RAM and a 20 GB hard drive. Two 100Mb NICs, a SIS onboard and a VIA PCI. The system runs smoothly with 2.1-RC2 and earlier versions, so I think the hardware is ok.
Can someone help me to debug this? There were significant network driver changes from 2.1-RC2 to 2.1-RELEASE?
My system settings don't have any exotic configurations, except for IPv6 with two gateways (the machine is at home). I have PowerD enabled and the default NIC optimizations.
-
I would definitely try disabling powerd. I don't think the Duron has any power saving features anyway.
Define 'hard lock', no response to the capslock on the keyboard?
Steve
-
Sorry… my english is not so good... :)
I mean a hardware hang, as opposed to software hang wich you can reset using CTRL-ALT-DEL...
This time the machine is totally unresponsive. It will stay at console menu and no answer by network anymore. Keystrokes on console does nothing.
Enabling or disabling PowerD appears to make no difference. I tried to do it on 2.1-RC2 too, and the only visible difference is HD stop spinning after some time.
With PowerD enabled or not, 2.1-RC2 works in both tests.
-
Sometimes a box can appear to hang bit it's not actually completely dead.
When it freezes does the keyboard Caps Lock or Num Lock key still work?
Try pressing Ctrl-T. It may give you some information on what process is causing the problem.Steve
-
Leftover bits and pieces from the old version have been a bit of an issue. I'd say backup settings, clean install 2.1 and restore settings.
While its indeed great fun tracking down bugs the fast easy way also has its merits.
-
I think he allready did that…... ;)
Hello guys,
I am experiencing some hard locks with 2.1-RELEASE. After some time the pfSense machine hangs requiring a press of reset button. No crash dumps, no logs, no kernel panics, no info at all.
I made a through memory test, nothing was found. I formatted HD and made a clean 2.1-RELEASE install. The box ran a day or so, then hanged needing to reset by button.
I went back to 2.1-RC2, the problem was gone. Then I upgraded to 2.1-RELEASE, the problem came back.
My machine is a old AMD Duron 1GHz, with 512MB of RAM and a 20 GB hard drive. Two 100Mb NICs, a SIS onboard and a VIA PCI. The system runs smoothly with 2.1-RC2 and earlier versions, so I think the hardware is ok.
Can someone help me to debug this? There were significant network driver changes from 2.1-RC2 to 2.1-RELEASE?
My system settings don't have any exotic configurations, except for IPv6 with two gateways (the machine is at home). I have PowerD enabled and the default NIC optimizations.
Leftover bits and pieces from the old version have been a bit of an issue. I'd say backup settings, clean install 2.1 and restore settings.
While its indeed great fun tracking down bugs the fast easy way also has its merits.
-
Maybe you should have send me this:
-
:D yes…..
-
Yeah - In that case I'm not sure whats up? And with no error messages its abit hard to figure out I imagine. Sucks.
-
Seems that 2.1 is alot more picky with hardware than 2.0.x was.
Its should actually be the other way round…
-
I didn't want to be the one to bring that up again, but yeah… Thats true.
I think it will get patched quick. -
I believe so too.
What power-scheme is the OP running?? When booting in, then it would be nice to know what scheme he is running and if he had tried with other options?
-
Not sure - Given the number of people having issues, I might advise to wait for the next patch and try again then. 2.03 was pretty stable for me.
-
I run 2.0.3 and dont intend to upgrade for that exact reason. Since the mainpart of mine are running in production, I cant afford to be the testbed for something thats not rock solid.
I have had 2.1 running in test environments and it works reasonably well. Since you know I use PPTP, it seems a little flaky in 2.1. And then my widescreen theme didnt work and that was a major bummer…
-
I can confirm I have the exact same issue. System completely unresponsive as well. From the console, the screen just shows the login prompt, but no keyboard events get registered, not even the caps lock, etc.
-
I can confirm too. I have 2 different boxes with same issue. Easy way to freeze the kernel in my case is using IGMPv2 on WAN + multicast.
-
I'm on the same boat! I have two almost identical hardware boxes and one of them keep on hanging randomly since 2.1 upgrade (more than 10 times now). Before that they've been running v2.x for years without ANY problem.
-
A random lockup could be any number of things so although these all appear to be the same situation you need to bare in mind they may be completely unrelated. If we assume they do they have a common cause if must be something fairly unusual to have not shown up in beta testing. Is there some commonality between your setups? Michael Sh. mentions multicast, are any of the rest of you in a multicast environment? Are you all running older hardware like the OP?
Steve
-
I have been observing this problem on 2.1. Since May 2012, when I became interested in the multicast.
For a long time trying to figure out what the reason, but so far without success. I have a lot pfsens'es under the supervision of an entirely different platforms, but for experiments using two home boxes:
Intel H55 - CPU G6950 2.80GHz - 2G RAM - re + em
Zotac NVIDIA nForce MCP79 (7A?) - CPU U2300 1.20GHz - 4G RAM - em + nfe + ath
Provider routers - Brocade Communications Systems, Inc.My ISP uses IGMPv2 for muiticast IP-TV and I use Local Peer Discovery (Transmission daemon). Sysctl net.inet.igmp.default_version=2 does not work as expected, so allow the passage of IGMP on the WAN. Kernel switches WAN to IGMPv2 and all works from 12 hours to about 5 days.
Enough to freeze two conditions - permits IGMP on WAN and permits LPD in Transmission. Without this uptime may be monthes.I was really hoping that 2.1 will be released on the basis of 8.4, as there are many changes in the locking in TCP/IP - maybe it would take away the problem. Maybe not just this one. For example crashes the kernel in the presence of IPv6 traffic and reconfigure the interface simultaneously.
Edit:
Both work on 2.1 amd64 from ALPHA. On the first enabled hardware whatchdog. How to use hardware whatchdog on NVIDIA nForce MCP79/7A I have never found. If someone tell me will be happy. -
Hi guys,
I was absent for some time since I downgraded to 2.1-RC2 (fully removed RELEASE and installed a clean RC2). All things are nice since then. So I wondering how do I do to debug what is the trouble. I wanna help to catch this bug, but since my system crashes with no info, I don't know how to start.
I already changed some bits of hardware (as NIC and other cards in PCI slots) and started with clean pfsense config, with no success. System hangs randomly. Sometimes it stays for 24 hours or more, sometimes it hangs on boot when kernel loads and first pfSense logo is shown. I have no ideas at this time.
My friend has other different machine and had same issue. I took my CD to him. So where are the old snapshots? I want to burn another CD of 2.1-RC2 in case of trouble.