PFSENSE Crash Report
-
Hi Everyone,
This is my first build of Pfsense. Just now encountered a crash report on the dash board. Could someone help me interpret this one.Appreciate so much to those who will reply and suggest what will I gonna do with it. I'm currently experiencing high latency as well on one of my NIC maybe this is one of the reason im having having latency.Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x40979b
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80e24910
stack pointer = 0x28:0xfffffe0000364760
frame pointer = 0x28:0xfffffe0000364790
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 = 0 (em0 taskq)
version.txt06000033613630277424 7625 ustarrootwheelFreeBSD 11.2-RELEASE-p4 #2 b00c407ba5d(RELENG_2_4_4): Mon Nov 26 11:41:48 EST 2018
root@buildbot2.nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSense -
That text does not contain enough information to determine what happened. It should have offered to let you download the crash report which would contain all of the available information.
Also you should be using 2.4.5, not 2.4.4.
-
Thank you so much for the prompt respond jimp. Actually here is the crash report file for more details crash report.txt
-
db:0:kdb.enter.default> bt Tracing pid 0 tid 100036 td 0xfffff80003c4c000 pppoe_findsession() at pppoe_findsession+0x70/frame 0xfffffe0000364790 ng_pppoe_rcvdata_ether() at ng_pppoe_rcvdata_ether+0x36b/frame 0xfffffe0000364830 ng_apply_item() at ng_apply_item+0x1a9/frame 0xfffffe00003648b0 ng_snd_item() at ng_snd_item+0x12f/frame 0xfffffe00003648f0 ether_demux() at ether_demux+0x23a/frame 0xfffffe0000364920 ether_nh_input() at ether_nh_input+0x32b/frame 0xfffffe0000364980 netisr_dispatch_src() at netisr_dispatch_src+0xa8/frame 0xfffffe00003649d0 ether_input() at ether_input+0x26/frame 0xfffffe00003649f0 if_input() at if_input+0xa/frame 0xfffffe0000364a00 lem_rxeof() at lem_rxeof+0x3ed/frame 0xfffffe0000364aa0 lem_handle_rxtx() at lem_handle_rxtx+0x32/frame 0xfffffe0000364ae0 taskqueue_run_locked() at taskqueue_run_locked+0x154/frame 0xfffffe0000364b40 taskqueue_thread_loop() at taskqueue_thread_loop+0x98/frame 0xfffffe0000364b70 fork_exit() at fork_exit+0x83/frame 0xfffffe0000364bb0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe0000364bb0
<6>ng0: changing name to 'pppoe0' <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session <5>ng_pppoe[14]: no matching session [... repeat a bunch more...]
I don't recall seeing that particular backtrace or set of errors recently (if ever). If this is a new setup then it's possible there is a hardware issue on that network card, or perhaps a bad interaction between the hardware and the OS. You might make sure that the BIOS is completely up-to-date.
-
Can you enlighten me a bit what part or line indicates there is the error?because literally I have no idea what I'm looking at.
-
Everything in my last post. The first part is the crash backtrace. It crashed while attempting to locate a PPPoE session (which is also indicated in the second part, the end of the system message buffer).
Looking back through the backtrace you can also see it was using "lem" which is Legacy em(4) which generally means you are using a rather old Intel network card. Nothing wrong with that per se, but depending on its age, and the age of the hardware in general, it could have a hardware issue.
-
This post is deleted! -
Hello, what problem is this?
Crash report begins. Anonymous machine information:amd64
11.2-RELEASE-p10
FreeBSD 11.2-RELEASE-p10 #9 4a2bfdce133(RELENG_2_4_4): Wed May 15 18:54:42 EDT 2019 root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfSense/tmp/FreeBSD-src/sys/pfSenseCrash report details:
No PHP errors found.
Filename: /var/crash/info.0
Dump header from device: /dev/label/swap0
Architecture: amd64
Architecture Version: 1
Dump Length: 71680
Blocksize: 512
Dumptime: Thu Aug 20 22:23:13 2020
Hostname: Pfsense5.mtz.jovenclub.cu
Magic: FreeBSD Text Dump
Version String: FreeBSD 11.2-RELEASE-p10 #9 4a2bfdce133(RELENG_2_4_4): Wed May 15 18:54:42 EDT 2019
root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-244/obj/amd64/ZfGpH5cd/build/ce-crossbuild-244/pfS
Panic String:
Dump Parity: 692791847
Bounds: 0
Dump Status: goodFilename: /var/crash/textdump.tar.0
ddb.txt?????????????????????????????????????????????????????????????????????????????????????????????0600????0???????0???????140000??????13717630021? 7072? ?????????????????????????????????????????????????????????????????????????????????????????????????????ustar???root????????????????????????????wheel??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????db:0:kdb.enter.default> run lockinfo
db:1:lockinfo> show locks
No such command; use "help" to list available commands
db:1:lockinfo> show alllocks
No such command; use "help" to list available commands
db:1:lockinfo> show lockedvnods
Locked vnodes
db:0:kdb.enter.default> show pcpu
cpuid = 0
dynamic pcpu = 0x898380
curthread = 0xfffff8000481d000: pid 12 "irq21: fxp0"
curpcb = 0xfffffe004d975cc0
fpcurthread = none
idlethread = 0xfffff800042e7000: tid 100003 "idle: cpu0"
curpmap = 0xffffffff82b85998
tssp = 0xffffffff82bb6810
commontssp = 0xffffffff82bb6810
rsp0 = 0xfffffe004d975cc0
gs32p = 0xffffffff82bbd068
ldt = 0xffffffff82bbd0a8
tss = 0xffffffff82bbd098
db:0:kdb.enter.default> bt
Tracing pid 12 tid 100066 td 0xfffff8000481d000
__mtx_lock_sleep() at __mtx_lock_sleep+0xcd/frame 0xfffffe004d975620
syncache_lookup() at syncache_lookup+0xc9/frame 0xfffffe004d975650
syncache_add() at syncache_add+0x16e/frame 0xfffffe004d9757a0
tcp_input() at tcp_input+0x1410/frame 0xfffffe004d9758e0
ip_input() at ip_input+0x139/frame 0xfffffe004d975940
netisr_dispatch_src() at netisr_dispatch_src+0xa8/frame 0xfffffe004d975990
ether_demux() at ether_demux+0x173/frame 0xfffffe004d9759c0
ether_nh_input() at ether_nh_input+0x32b/frame 0xfffffe004d975a20
netisr_dispatch_src() at netisr_dispatch_src+0xa8/frame 0xfffffe004d975a70
ether_input() at ether_input+0x26/frame 0xfffffe004d975a90
if_input() at if_input+0xa/frame 0xfffffe004d975aa0
fxp_intr() at fxp_intr+0x411/frame 0xfffffe004d975b20
intr_event_execute_handlers() at intr_event_execute_handlers+0xe9/frame 0xfffffe004d975b60
ithread_loop() at ithread_loop+0xe7/frame 0xfffffe004d975bb0
fork_exit() at fork_exit+0x83/frame 0xfffffe004d975bf0
fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe004d975bf0
--- trap 0, rip = 0, rsp = 0, rbp = 0 ---
db:0:kdb.enter.default> ps