Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Fatal trap 12: page fault while in kernel mode

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 3 Posters 475 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      plastikman
      last edited by

      Hello,
      This is my second crash in last month, same error on both.
      pfSense version: 2.4.5-RELEASE

      extracted from system.log:

      syslogd: kernel boot file is /boot/kernel/kernel
      kernel: 
      kernel: 
      kernel: 
      kernel: Fatal trap 12: page fault while in kernel mode
      kernel: 
      kernel: Fatal trap 12: page fault while in kernel mode
      kernel: cpuid = 3; apic id = 06
      kernel: fault virtual address	= 0x3520030519
      kernel: cpuid = 2; fault code		= supervisor read data, page not present
      kernel: apic id = 04
      kernel: instruction pointer	= 0x20:0xffffffff80e8127a
      kernel: stack pointer	        = 0x28:0xfffffe0239a0b0d0
      kernel: frame pointer	        = 0x28:0xfffffe0239a0b150
      kernel: code segment		= base 0x0, limit 0xfffff, type 0x1b
      kernel: 			= DPL 0, pres 1, long 1, def32 0, gran 1
      kernel: processor eflags	= interrupt enabled, resume, IOPL = 0
      kernel: current process		= 12 (irq276: vmx1)
      kernel: fault virtual address	= 0x3520030519
      kernel: trap number		= 12
      kernel: fault code		= supervisor read data, page not present
      kernel: panic: page fault
      kernel: cpuid = 3
      kernel: KDB: enter: panic
      

      textdump.tar.0 info.0

      Also maybe worth mentioning, after system booted "dpinger" caused very high CPU load which never resolved after multiple reboots so I had to disable "dpinger" service.

      All help is appreciated, I can provide more information if needed.
      Thanks !

      K 1 Reply Last reply Reply Quote 0
      • K
        kprovost @plastikman
        last edited by

        @plastikman That's an impressively old version to be running.

        Realistically that's not going to get investigated. Try upgrading to 2.7.2 and see if it happens there.

        1 Reply Last reply Reply Quote 2
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Backtrace for reference:

          db:0:kdb.enter.default>  bt
          Tracing pid 12 tid 100127 td 0xfffff8000908b000
          kdb_enter() at kdb_enter+0x3b/frame 0xfffffe02399d78f0
          vpanic() at vpanic+0x19b/frame 0xfffffe02399d7950
          panic() at panic+0x43/frame 0xfffffe02399d79b0
          trap_pfault() at trap_pfault/frame 0xfffffe02399d7a00
          trap_pfault() at trap_pfault+0x49/frame 0xfffffe02399d7a60
          trap() at trap+0x29d/frame 0xfffffe02399d7b70
          calltrap() at calltrap+0x8/frame 0xfffffe02399d7b70
          --- trap 0xc, rip = 0xffffffff80f7eb95, rsp = 0xfffffe02399d7c40, rbp = 0xfffffe02399d7e40 ---
          pf_test() at pf_test+0x1ef5/frame 0xfffffe02399d7e40
          pf_check_out() at pf_check_out+0x1d/frame 0xfffffe02399d7e60
          pfil_run_hooks() at pfil_run_hooks+0x90/frame 0xfffffe02399d7ef0
          ip_output() at ip_output+0xa53/frame 0xfffffe02399d8020
          ip_forward() at ip_forward+0x2c3/frame 0xfffffe02399d80c0
          ip_input() at ip_input+0x724/frame 0xfffffe02399d8150
          netisr_dispatch_src() at netisr_dispatch_src+0xa2/frame 0xfffffe02399d81a0
          ether_demux() at ether_demux+0x15b/frame 0xfffffe02399d81d0
          ether_nh_input() at ether_nh_input+0x32c/frame 0xfffffe02399d8230
          netisr_dispatch_src() at netisr_dispatch_src+0xa2/frame 0xfffffe02399d8280
          ether_input() at ether_input+0x26/frame 0xfffffe02399d82a0
          vmxnet3_rxq_eof() at vmxnet3_rxq_eof+0x752/frame 0xfffffe02399d8330
          vmxnet3_legacy_intr() at vmxnet3_legacy_intr+0xe0/frame 0xfffffe02399d8360
          intr_event_execute_handlers() at intr_event_execute_handlers+0xe9/frame 0xfffffe02399d83a0
          ithread_loop() at ithread_loop+0xe7/frame 0xfffffe02399d83f0
          fork_exit() at fork_exit+0x83/frame 0xfffffe02399d8430
          fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe02399d8430
          --- trap 0, rip = 0, rsp = 0, rbp = 0 ---
          

          But, yes, many many things have been fixed since 2.4.5 so test in a current version.

          Also check the VMWare hypervisor and VM versions you are running.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.