Crashing on new hardware with Fatal trap 12: page fault while in kernel mode
-
Has anyone tested the latest releases? Is it safe to upgrade again?
-
Seems to be stable again, but you can always downgrade with a backup.tgz on full installs or switch slices on nano.
FTP still does not work very good with the sites I have tested, tough. -
Hi,
we have this crashes too… dependent on hardware it gaves a TRAP 12 (attached image with firmware from July, 4th).
Other hardware get stucked without any hint what happened.
Yesterday evening updated to
2.1-RC0 (amd64)
built on Mon Jul 8 21:53:11 EDT 2013
FreeBSD 8.3-RELEASE-p8
because last possible version to download was from July, 2nd. But still same problem…Has someone a link to a stable version from July, 1st please (older version is from April, 22th so rolling back is not so nice)?
Thanks.
-
No such problem with Tue Jul 9 11:08:17 EDT 2013 FreeBSD 8.3-RELEASE-p8. However, the patches do nothing useful to improve FTP, in fact they break things badly here (not as in kernel panic, but breaking FTP functionality which was working perfectly fine before).
https://redmine.pfsense.org/issues/3077#note-3
I don't see how these regressions are good at this stage. There is a crapload more users with normal FTP usage, as opposed to esoteric multi-WAN scenarios these were supposed to improve.
-
Here the actual crashdump output of yesterday firmware:
Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x90 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff802122cf stack pointer = 0x28:0xffffff8055b9cac0 frame pointer = 0x28:0xffffff8055b9cad8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 8 (pfpurge)I found in it also Interesting snippet from yesterday install/update part which could cause problems, too:
<118>Configuring crash dumps…
<118>Using /dev/ad6s1b for dump device.
<118>Mounting filesystems...
ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
Consider tuning vm.kmem_size and vm.kmem_size_max
in /boot/loader.conf.
ZFS filesystem version 5
ZFS storage pool version 28
<118>Disabling APM on /dev/ad6Edit these are the default parameters setup by installer (June 4th):
[2.1-RC0][root@gw1.zws8.local]/root(1): cat /boot/loader.conf
autoboot_delay="3"
vm.kmem_size="435544320"
vm.kmem_size_max="535544320"
kern.ipc.nmbclusters="0"
hw.usb.no_pf="1" -
I don't see how these regressions are good at this stage. There is a crapload more users with normal FTP usage, as opposed to esoteric multi-WAN scenarios these were supposed to improve.
Well, FTP is broken on my second WAN link, too. I could swear it used to work about 2 month ago…
-
I found in it also Interesting snippet from yesterday install/update part which could cause problems, too:
Edit these are the default parameters setup by installer (June 4th):
[2.1-RC0][root@gw1.zws8.local]/root(1): cat /boot/loader.conf
autoboot_delay="3"
vm.kmem_size="435544320"
vm.kmem_size_max="535544320"
kern.ipc.nmbclusters="0"
hw.usb.no_pf="1"mmh, I changed this to
vm.kmem_size="536870912"
vm.kmem_size_max="1073741824"
didnt helped. It crashed 3 time again since then… -
Has anyone updated to the latest snapshots? Is it safe to upgrade again? Any feedback from you guys here?
-
Yes, I'm running the latest snapshot. For me, it's rock-solid again since a few days.
-
Have you tryed small partitions ?
I had a problem with all pfsense version on a new computer with a partition size higher than ~32Gb (can't be 100% sure about the actual size at witch it does not work)