My Pfsense has crashed

djdeito

My Pfsense has crashed. i would appreciate if someone could help me identify the cause of the crash. Please see the attached crash files.textdump.tar.0 info.0

stephenw10

Hmm, I've seen that once before but I don't think we ever found the cause.
Is this the first time you've seen it crash?

Backtrace:

db:0:kdb.enter.default>  bt
Tracing pid 73357 tid 100193 td 0xfffff80009eed740
kdb_enter() at kdb_enter+0x37/frame 0xffffffff83dba530
vpanic() at vpanic+0x197/frame 0xffffffff83dba580
panic() at panic+0x43/frame 0xffffffff83dba5e0
trap_fatal() at trap_fatal+0x391/frame 0xffffffff83dba640
trap_pfault() at trap_pfault+0x4f/frame 0xffffffff83dba690
trap() at trap+0x286/frame 0xffffffff83dba7a0
calltrap() at calltrap+0x8/frame 0xffffffff83dba7a0
--- trap 0xc, rip = 0xffffffff8136e5fa, rsp = 0xffffffff83dba870, rbp = 0xffffffff83dba890 ---
free_pv_entry() at free_pv_entry+0x4a/frame 0xffffffff83dba890
pmap_remove_pte() at pmap_remove_pte+0x1c5/frame 0xffffffff83dba8f0
pmap_remove_ptes() at pmap_remove_ptes+0xdc/frame 0xffffffff83dba950
pmap_remove() at pmap_remove+0x3b3/frame 0xffffffff83dba9e0
vm_map_delete() at vm_map_delete+0x161/frame 0xffffffff83dbaa40
kern_munmap() at kern_munmap+0x91/frame 0xffffffff83dbaac0
amd64_syscall() at amd64_syscall+0x387/frame 0xffffffff83dbabf0
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xffffffff83dbabf0
--- syscall (73, FreeBSD ELF64, sys_munmap), rip = 0x800b3806a, rsp = 0x7fffffffe3e8, rbp = 0x7fffffffe420 ---

Steve

djdeito

@stephenw10 This is the first time i see this crash.

stephenw10

Or any crash?

djdeito

@stephenw10 Maybe two or three months ago my Pfsense crashed (for the first time) and i believed it was because i had configured an additional Openvpn instance but with TCP 443 (i currently have two Openvpn instances, one with UDP 443 and the other with TCP 443) i mostly use UDP and have the TCP as a backup. My Pfsense web management is on a different port.

i was hoping the crash report would point out the cause of the crash. i am going to do some trial-and-error, first by replacing the SSD and then disabling the Openvpn TCP instance.

stephenw10

Hmm, unfortunately it doesn't point to anything specific.

We saw the same thing here: https://forum.netgate.com/post/931240
But in a much older version which makes it look like a more general problem, like bad RAM perhaps.

djdeito

@stephenw10 The first time Pfsense crashed two or three months ago, i ran the Dell's diagnostic and it found no errors on the RAM. Then at around three days before the second Pfsense crash, out of curiosity i ran a Memtest86 and it did not find any errors on the RAM either. I don't mind replacing the RAM and is one of the items in my trial-and-error list. i have replaced the SSD at this point.

stephenw10

Do you know if the crashes were all identical? Probably not RAM if they were.

djdeito

@stephenw10 i did not pay much attention to the crash report during the first crash so i cannot say for sure if the second crash is identical to the first. But, i was using Openvpn TCP 443 when the first crash happened and i was using Openvpn UDP 443 when the second crash happened. i am waiting to see if Pfsense crashes again after replacing the SSD, if it does, i will start digging into the Openvpn settings.

stephenw10

I'd be surprised if it's anything to do with OpenVPN to be honest. Both times we saw it it appeared to be in php.

djdeito

@stephenw10 if it is a php issue, could it also be related to hardware?

stephenw10

Unlikely IMO. Hardware errors are usually more random.