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

    Crash during reboots

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 487 Views 2 Watching
    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.
    • M Offline
      mikekoke
      last edited by

      Hi everyone, lately i am having some crashes during reboots and i would like to ask you if anyone is kind enough to look at the log in the file and tell me what the problem would be.
      Thank you very much to those who can help me.

      Log.txt

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

        The key parts of that are:

        db:0:kdb.enter.default>  show pcpu
        cpuid        = 3
        dynamic pcpu = 0xfffffe03e2a9f580
        curthread    = 0xfffff80015831620: pid 370 "logger"
        curpcb       = 0xfffffe03db086b00
        fpcurthread  = 0xfffff80015831620: pid 370 "logger"
        idlethread   = 0xfffff80005f7f620: tid 100006 "idle: cpu3"
        curpmap      = 0xfffff8000ffc5138
        tssp         = 0xffffffff835a3408
        commontssp   = 0xffffffff835a3408
        rsp0         = 0xfffffe03db086b00
        gs32p        = 0xffffffff835aa060
        ldt          = 0xffffffff835aa0a0
        tss          = 0xffffffff835aa090
        tlb gen      = 1434
        db:0:kdb.enter.default>  bt
        Tracing pid 370 tid 100186 td 0xfffff80015831620
        kdb_enter() at kdb_enter+0x3b/frame 0xfffffe03db086420
        vpanic() at vpanic+0x19b/frame 0xfffffe03db086480
        panic() at panic+0x43/frame 0xfffffe03db0864e0
        trap_pfault() at trap_pfault/frame 0xfffffe03db086530
        trap_pfault() at trap_pfault+0x49/frame 0xfffffe03db086590
        trap() at trap+0x29d/frame 0xfffffe03db0866a0
        calltrap() at calltrap+0x8/frame 0xfffffe03db0866a0
        --- trap 0xc, rip = 0xffffffff8125815e, rsp = 0xfffffe03db086770, rbp = 0xfffffe03db086770 ---
        copyout() at copyout+0x3e/frame 0xfffffe03db086770
        uiomove_faultflag() at uiomove_faultflag+0xf4/frame 0xfffffe03db0867b0
        pipe_read() at pipe_read+0x203/frame 0xfffffe03db086820
        dofileread() at dofileread+0xba/frame 0xfffffe03db086860
        kern_readv() at kern_readv+0x68/frame 0xfffffe03db0868b0
        sys_read() at sys_read+0x84/frame 0xfffffe03db086900
        amd64_syscall() at amd64_syscall+0xa86/frame 0xfffffe03db086a30
        fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe03db086a30
        --- syscall (3, FreeBSD ELF64, sys_read), rip = 0x80096af4a, rsp = 0x7fffffffe728, rbp = 0x7fffffffe740 ---
        db:0:kdb.enter.default>  ps
        

        and

        <118>Launching the init system...Updating CPU Microcode...
        
        
        Fatal trap 12: page fault while in kernel mode
        cpuid = 3; apic id = 13
        fault virtual address	= 0x800e2b000
        fault code		= supervisor write data, page not present
        instruction pointer	= 0x20:0xffffffff8125815e
        stack pointer	        = 0x28:0xfffffe03db086770
        frame pointer	        = 0x28:0xfffffe03db086770
        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		= 370 (logger)
        trap number		= 12
        panic: page fault
        cpuid = 3
        

        Does it always fail in the same way?

        That sort of crash can be hard to pin down. If it doesn't fail the same way each time I would look at bad ram.

        Steve

        1 Reply Last reply Reply Quote 0
        • M Offline
          mikekoke
          last edited by

          It crashes more frequently during reboots, but it also happens when I turn it on normally after cleaning.
          The system is on a machine and is not virtualized.
          How can I provide you with further details to identify the problem?
          Thank you.

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

            The important question there is if the crash reports are similar or identical even.

            If they are it may be a software issue. If they are different every time it's probably a hardware problem, most likely bad ram. Though if it was I might expect it to crash at random times not just at boot.

            Steve

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