Fatal trap 9 general protection fault while in kernel mode
-
What is up with all those ifconfigs ?
Can you show a trace or screenshot of this happening?
Can you type bt at the prompt when this happens?
Can you provide logs? -
@ermal:
What is up with all those ifconfigs ?
Really don't know )
Can you show a trace or screenshot of this happening?
Can you type bt at the prompt when this happens?
Sorry, can't at this time
Can you provide logs?In logs there is errors like:
Approaching the limit on PV entries, the consider increasing either vm.pmap.shpgperproc sysctl…
-
By the way. How Cpative portal organized in 2.0?
In 1.2.3 it was done with one ipfw fwd rule to portal page and rules before it to pass traffic to internet for authorized users.
How authorized users going to internet in 2.0?
Every time when I forward my 3000 users to captive portal it goes down with CPU for system = 90% and whole CPU 100% -
I am having the same issue. I run my routers as VM's on a Xenserver machine running an AMD Athlon II x2 chip and have never been able to get pfSense 2 to load. I get the same "Fatal Trap 9" error you are getting every time I try and install it.
-
Just tried to upgrade one of my 1.2.3 installs and got the same Fatal Trap 9 error. So both the full install and the upgrade resulted in the same error. Are most people running this on an Intel chip and therefore not having this issue? Is this an error with all AMD installs or am I just unlucky? If it is with all AMD chips, I am surprised a bug this big could make it to a RC version.
-
I got it on HP blade servers, adn HP DL160
-
Is that running an AMD chip?
-
Intel Xeon. But this error appears only on moments of high load. So system booting normally.
-
I can't get the boot. Has anyone got 2.0 to run on an AMD chip? What about as a VM in Xenserver?
-
I can't get the boot. Has anyone got 2.0 to run on an AMD chip? What about as a VM in Xenserver?
I'm running 2.0-RC1-amd64 snapshot built 3/18/2011 on AMD chip. Specifically, inside VMware Player 3.1.3 on Windows 7 x64 using AMD Phenom II X3 720 CPU.
Seems to be running fine, except:
1. "watchdog timeout" messages spamming console (known issue with em0)
2. updating erases this line inside /etc/sysctl.conf: kern.timecounter.hardware=i8254Both issues are already known at:
http://redmine.pfsense.org/projects/pfsense-tools/issues?set_filter=1&tracker_id=1