Crash Cycle on Disabling firewall

olorinpc

Ok - somehow I got into a cycle of crashing in relation to "disable firewall" (I was attempting to fully rule out firewall as the prob behind crashplan not connecting)

I checked the box and hit save, then went into a weird cycle of constant crashing, not enabling me to undo that action. On latest pfsense - 2.1.2 release.

Crash report below - any ideas?

For reference…. the last cycle it seems i was able to resave enabling the firewall quickly enough, and the crash cycle has halted, bringing me back to stable state... but, what went wrong here?

Crash report begins. Anonymous machine information:

i386
8.3-RELEASE-p15
FreeBSD 8.3-RELEASE-p15 #1: Thu Apr 10 05:45:21 EDT 2014 root@pf2_1_1_i386.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386

Crash report details:

Filename: /var/crash/bounds
6

Filename: /var/crash/info.0
Dump header from device /dev/ad0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 145879040B (139 MB)
Blocksize: 512
Dumptime: Thu May 1 19:24:04 2014
Hostname: olonet.home
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.3-RELEASE-p15 #1: Thu Apr 10 05:45:21 EDT 2014
root@pf2_1_1_i386.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
Panic String: page fault
Dump Parity: 3288982887
Bounds: 0
Dump Status: good

Filename: /var/crash/info.1
Dump header from device /dev/ad0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 199245824B (190 MB)
Blocksize: 512
Dumptime: Thu May 1 19:27:11 2014
Hostname: olonet.home
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.3-RELEASE-p15 #1: Thu Apr 10 05:45:21 EDT 2014
root@pf2_1_1_i386.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
Panic String: page fault
Dump Parity: 1069200484
Bounds: 1
Dump Status: good

Filename: /var/crash/info.2
Dump header from device /dev/ad0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 202784768B (193 MB)
Blocksize: 512
Dumptime: Thu May 1 19:29:59 2014
Hostname: olonet.home
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.3-RELEASE-p15 #1: Thu Apr 10 05:45:21 EDT 2014
root@pf2_1_1_i386.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
Panic String: page fault
Dump Parity: 1740325475
Bounds: 2
Dump Status: good

Filename: /var/crash/info.3
Dump header from device /dev/ad0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 202891264B (193 MB)
Blocksize: 512
Dumptime: Thu May 1 19:32:55 2014
Hostname: olonet.home
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.3-RELEASE-p15 #1: Thu Apr 10 05:45:21 EDT 2014
root@pf2_1_1_i386.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
Panic String: page fault
Dump Parity: 3608888163
Bounds: 3
Dump Status: good

Filename: /var/crash/info.4
Dump header from device /dev/ad0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 202919936B (193 MB)
Blocksize: 512
Dumptime: Thu May 1 19:37:18 2014
Hostname: olonet.home
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.3-RELEASE-p15 #1: Thu Apr 10 05:45:21 EDT 2014
root@pf2_1_1_i386.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
Panic String: page fault
Dump Parity: 3735309411
Bounds: 4
Dump Status: good

Filename: /var/crash/info.5
Dump header from device /dev/ad0s1b
Architecture: i386
Architecture Version: 2
Dump Length: 111374336B (106 MB)
Blocksize: 512
Dumptime: Thu May 1 19:42:21 2014
Hostname: olonet.home
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 8.3-RELEASE-p15 #1: Thu Apr 10 05:45:21 EDT 2014
root@pf2_1_1_i386.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386
Panic String: page fault
Dump Parity: 2374367081
Bounds: 5
Dump Status: good

Filename: /var/crash/minfree
2048

jimp

Did you submit those crash reports once things settled down? There isn't enough info in the summary to tell anything.

I also didn't see any submitted reports from the IP address that you posted this message from. If it's submitted from a different IP address, send me a PM with the actual IP and I'll check the reports.

olorinpc

Hrm - unfortunately the submit crash report option came up in the middle of the cycle, so yes I submitted, but you confirmed my guess that they didn't make it through.

I will try to dig into the logs and see if I can find anything more useful.

It has been stable again since I undid that test, so have been a little cautious playing with too much :)