Help Understanding a Crash [kernel panic]

stephenw10

You have the backtrace from the crash report?

None 0

stephenw10

Mmm, well very similar but not identical:

db:0:kdb.enter.default>  bt
Tracing pid 40766 tid 100593 td 0xfffff8013f829740
kdb_enter() at kdb_enter+0x37/frame 0xfffffe00910f4530
vpanic() at vpanic+0x197/frame 0xfffffe00910f4580
panic() at panic+0x43/frame 0xfffffe00910f45e0
trap_fatal() at trap_fatal+0x391/frame 0xfffffe00910f4640
trap_pfault() at trap_pfault+0x4f/frame 0xfffffe00910f4690
trap() at trap+0x286/frame 0xfffffe00910f47a0
calltrap() at calltrap+0x8/frame 0xfffffe00910f47a0
--- trap 0xc, rip = 0xffffffff8120874b, rsp = 0xfffffe00910f4870, rbp = 0xfffffe00910f4880 ---
vm_radix_remove() at vm_radix_remove+0x1b/frame 0xfffffe00910f4880
vm_page_free_prep() at vm_page_free_prep+0x55/frame 0xfffffe00910f48a0
vm_page_free_toq() at vm_page_free_toq+0x12/frame 0xfffffe00910f48d0
vm_object_page_remove() at vm_object_page_remove+0x61/frame 0xfffffe00910f4930
vm_map_entry_delete() at vm_map_entry_delete+0x104/frame 0xfffffe00910f4980
vm_map_delete() at vm_map_delete+0x184/frame 0xfffffe00910f49e0
vm_map_remove() at vm_map_remove+0xab/frame 0xfffffe00910f4a10
vmspace_exit() at vmspace_exit+0xcb/frame 0xfffffe00910f4a50
exit1() at exit1+0x55b/frame 0xfffffe00910f4ab0
sys_sys_exit() at sys_sys_exit+0xd/frame 0xfffffe00910f4ac0
amd64_syscall() at amd64_syscall+0x387/frame 0xfffffe00910f4bf0
fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfffffe00910f4bf0
--- syscall (1, FreeBSD ELF64, sys_sys_exit), rip = 0x800c2a00a, rsp = 0x7fffffffec38, rbp = 0x7fffffffec50 ---

What is that running on?

None 0

@stephenw10

What is that running on?

Sorry, what you mean?

bmeeks

@none-0 said in Help Understanding a Crash [kernel panic]:

@stephenw10

What is that running on?

Sorry, what you mean?

I suspect he means what type of hardware -- Netgate appliance (and if so, which model, as different models have different CPU families) or generic Intel/AMD hardware.

None 0

@bmeeks @stephenw10

It's a generic Intel box:
CPU: i3-4170
RAM: Kingston 2x8GB
Mobo: Asus (don't remember the model, but I can check)
Network adp: Intel I350-T4V2

stephenw10

Mmm, well I would be running a RAM test there when you can to be sure it's not hardware issue.
Though it seems far too similar to be a RAM error which is usually pretty random.

None 0

@stephenw10 I think I ll buy a new stick... Memory tests work sometimes, but for intermittent problems I would possible need to run them for days...
I can do the tests with more time, and use them elsewhere if happens to be no problem with.

A single module would do the trick, or dual channel benefits pfsense? I mean, it won't use the bandwidth, but latency is better in dual too... What do you guys think?

stephenw10

Unlikely to make much difference IMO. For a test it doesn't really matter anyway.

Steve

None 0

Hello,

Just to update about the crashs: they didn't happen again.
Also, I've being using Suricata 6.0.3 release since than, and no netmap issues

So, I changed my RAM, and tested the old ones:
24H of MemTest86+ and at least 5hrs of GoldMemory (not the best tests, but still), resulted in not a single red flag for them (tested individually), AND I'm using them on other Win machines withouth BSOD or anything in the logs.

I already saw RAM tests failing to detect problems, so based on what you explained, I'm assuming that both 1 - the issue with Suricata's Multithreading ring access, and 2 - darkstat, were hitting some intermittent problem, that I could not with tests and other OS.

Anyway, thank you for helping me out solving this. Really appreciate @stephenw10 and @bmeeks !