Fatal trap 12: page fault while in kernel mode



  • pfSense 2.3.4-RELEASE-p1 (i386 nanobsd)
    seems to have started a few weeks after upgrading to this version, before it was very stable
    reboots at least once a day i have attached the console output which shows the bt

    can anyone offer me some guidance on what the issue may be

    kernel trap 12 with interrupts disabled
    
    Fatal trap 12: page fault while in kernel mode
    cpuid = 0; apic id = 00
    fault virtual address    = 0x4
    fault code        = supervisor read, page not present
    instruction pointer    = 0x20:0xc1296e49
    stack pointer            = 0x28:0xda7f4aa4
    frame pointer            = 0x28:0xda7f4af4
    code segment        = base 0x0, limit 0xfffff, type 0x1b
                = DPL 0, pres 1, def32 1, gran 1
    processor eflags    = resume, IOPL = 0
    current process        = 11 (idle: cpu0)
    [ thread pid 11 tid 100003 ]
    Stopped at      in_cksum_skip+0x519:    movl    0(%ebx),%ebx
    db:0:kdb.enter.default> textdump set
    textdump set
    db:0:kdb.enter.default>  capture on
    db:0:kdb.enter.default>  run lockinfo
    db:1:lockinfo> show locks
    No such command
    db:1:locks>  show alllocks
    No such command
    db:1:alllocks>  show lockedvnods
    Locked vnodes
    db:0:kdb.enter.default>  show pcpu
    cpuid        = 0
    dynamic pcpu = 0x5c0b80
    curthread    = 0xc66f7000: pid 11 "idle: cpu0"
    curpcb       = 0xda7f4d40
    fpcurthread  = none
    idlethread   = 0xc66f7000: tid 100003 "idle: cpu0"
    APIC ID      = 0
    currentldt   = 0x50
    ```[pfsense console crash.txt](/public/_imported_attachments_/1/pfsense console crash.txt)


  • Hi,

    99 % sure its a hardware failure, FreeBSD freaks out during its idle loop and knowing that this loop is by far the most executed code on every device, I consider it without bugs  ;)
    The only thing you can do : check out the RAM and storage of your device.

    edit : if possible - and if present, change the power block and use an UPS.


Log in to reply