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

    Problem: pfSense reboot randomly

    Scheduled Pinned Locked Moved General pfSense Questions
    2 Posts 2 Posters 465 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.
    • F
      freebeebr
      last edited by

      pfSense randomly is rebooting.
      In crash log i have this:
      118>32-bit compatibility ldconfig path:
      <118>done.
      <118>>>> Removing vital flag from php72... failed.
      <118>External config loader 1.0 is now starting...
      <118>Launching the init system...Updating CPU Microcode...

      Fatal trap 12: page fault while in kernel mode
      cpuid = 2; apic id = 12
      fault virtual address = 0x800e29000
      fault code = supervisor write data, page not present
      instruction pointer = 0x20:0xffffffff8125815e
      stack pointer = 0x28:0xfffffe010fbfd770
      frame pointer = 0x28:0xfffffe010fbfd770
      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 = 348 (logger)
      trap number = 12
      panic: page fault
      cpuid = 2
      KDB: enter: panic
      panic.txt0600001213671165374 7146 ustarrootwheelpage faultversion.txt06000033013671165374 7624 ustarrootwheelFreeBSD 11.3-STABLE #243 abf8cba50ce(RELENG_2_4_5): Tue Jun 2 17:53:37 EDT 2020
      root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-245/obj/amd64/YNx4Qq3j/build/ce-crossbuild-245/sources/FreeBSD-src/sys/pfSense

      In attach i upload the two files for analyses. The CPU is a AMD FX(tm)-8350 Eight-Core Processor.
      The RAM Memory was tested by memtest and everything is ok. Always reboot on microcode part and is randomly (sometimes boot ok, other times not boot).

      info.0 textdump.tar.0

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        db:0:kdb.enter.default>  bt
        Tracing pid 348 tid 100193 td 0xfffff8000b866620
        kdb_enter() at kdb_enter+0x3b/frame 0xfffffe010fbfd420
        vpanic() at vpanic+0x19b/frame 0xfffffe010fbfd480
        panic() at panic+0x43/frame 0xfffffe010fbfd4e0
        trap_pfault() at trap_pfault/frame 0xfffffe010fbfd530
        trap_pfault() at trap_pfault+0x49/frame 0xfffffe010fbfd590
        trap() at trap+0x29d/frame 0xfffffe010fbfd6a0
        calltrap() at calltrap+0x8/frame 0xfffffe010fbfd6a0
        --- trap 0xc, rip = 0xffffffff8125815e, rsp = 0xfffffe010fbfd770, rbp = 0xfffffe010fbfd770 ---
        copyout() at copyout+0x3e/frame 0xfffffe010fbfd770
        uiomove_faultflag() at uiomove_faultflag+0xf4/frame 0xfffffe010fbfd7b0
        pipe_read() at pipe_read+0x203/frame 0xfffffe010fbfd820
        dofileread() at dofileread+0xba/frame 0xfffffe010fbfd860
        kern_readv() at kern_readv+0x68/frame 0xfffffe010fbfd8b0
        sys_read() at sys_read+0x84/frame 0xfffffe010fbfd900
        amd64_syscall() at amd64_syscall+0xa86/frame 0xfffffe010fbfda30
        fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe010fbfda30
        --- syscall (3, FreeBSD ELF64, sys_read), rip = 0x80096af4a, rsp = 0x7fffffffe728, rbp = 0x7fffffffe740 ---
        
        Fatal trap 12: page fault while in kernel mode
        cpuid = 2; apic id = 12
        fault virtual address	= 0x800e29000
        fault code		= supervisor write data, page not present
        instruction pointer	= 0x20:0xffffffff8125815e
        stack pointer	        = 0x28:0xfffffe010fbfd770
        frame pointer	        = 0x28:0xfffffe010fbfd770
        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		= 348 (logger)
        trap number		= 12
        panic: page fault
        cpuid = 2
        KDB: enter: panic
        

        Looks like a storage or filesystem problem to me. Reboot into single user mode and run fsck -y / no less than 5 times (until it neither finds problems or fixes problems), then reboot and see if it's better.

        Though given the nature of the backtrace I'm more inclined to think it's a storage/disk failure or maybe disk controller/cable failure.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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