Regular kernel panics on 2.4.3-RELEASE-p1

mr_gazza

Pfsense 2.4.3-RELEASE-p1 running on Qotom Q190G4, has been running perfectly for months but in the last week or so has started crashing regularly.
Nothing fancy in the configuration, DHCP, DNS, some NAT rules, no VPN, no HA, no captive portal.
Crash dump here: https://www.dropbox.com/s/3jtvrlswdd89xoe/dump.txt?dl=0
I've removed all added packages and set the following options in loader.conf to no avail:
kern.ipc.nmbclusters="1000000"
hw.igb.num_queues=1
Any ideas?

Gertjan

@mr_gazza said in Regular kernel panics on 2.4.3-RELEASE-p1:
....

I've removed all added packages and set the following options in loader.conf to no avail:
kern.ipc.nmbclusters="1000000"
hw.igb.num_queues=1
Any ideas?

Changing /boot/loader.conf wn't survive a reboot. pfSense will rewrite it.
Your own changes should be placed in /boot/loader.conf.local

Btw : your pfSense, or actually, FreeBSD, uses probably other drivers as I do - but I can assure you that you and I use the same "pfSense".
Generally, when crashes happens :
Check memory usage.
Change the power supply, change your UPS.
Change the hardware - the device pfSense is running on.

For example, I'm running pfSEnse on a 12 year old Dell Dimensuion :
Intel(R) Pentium(R) 4 CPU 3.20GHz
Current: 2800 MHz, Max: 3200 MHz
2 CPUs: 1 package(s) x 2 hardware threads
AES-NI CPU Crypto: No

Last crash I saw - and it was me fckng up the system : it was somewhere in 2016.

stephenw10

I'd have to guess bad RAM.

db:0:kdb.enter.default>  bt
Tracing pid 4632 tid 100255 td 0xfffff800a70655c0
pmap_remove_pages() at pmap_remove_pages+0x5f0/frame 0xfffffe0118268580
exec_new_vmspace() at exec_new_vmspace+0x19c/frame 0xfffffe01182685f0
exec_elf64_imgact() at exec_elf64_imgact+0x8d8/frame 0xfffffe01182686e0
kern_execve() at kern_execve+0x77c/frame 0xfffffe0118268a40
sys_execve() at sys_execve+0x4a/frame 0xfffffe0118268ac0
amd64_syscall() at amd64_syscall+0xa4c/frame 0xfffffe0118268bf0
fast_syscall_common() at fast_syscall_common+0x106/frame 0x7fffffffe380
db:0:kdb.enter.default>  ps

Do you have any further crashes? Do they look identical or more random?

Bad RAM usually results in relatively random crash logs. That can also start happening spontaneously.

Possibly a bad drive.

Steve