2.4 RC 2.4.0.r.20170920.2005 "kernel trap 12 with interrupts disabled"

  • kernel trap 12 with interrupts disabled
    Fatal trap 12: page fault while in kernel mode
    cpuid = 1; apic id = 02
    fault virtual address	= 0x30
    fault code		= supervisor read data, page not present
    instruction pointer	= 0x20:0xffffffff80cb9cfc
    stack pointer	        = 0x28:0xfffffe0118c0e450
    frame pointer	        = 0x28:0xfffffe0118c0e480
    code segment		= base 0x0, limit 0xfffff, type 0x1b
    			= DPL 0, pres 1, long 1, def32 0, gran 1
    processor eflags	= resume, IOPL = 0
    current process		= 75923 (sh)
    version.txt06000026713161004020  7603 ustarrootwheelFreeBSD 11.0-RELEASE-p12 #52 aced61fcbcd(RELENG_2_4_0): Wed Sep 20 20:11:24 CDT 2017

    Any ideas what this is and how to fix? Note this system ran 2.3.* for months, only real change was wipe/reload with 2.4 w/ ZFS and restore config.

    Also submitted crash log as i'm posting this. +/- 1 min.

  • Rebel Alliance Developer Netgate

    Not enough in that block to tell anything. Need to see at least the backtrace and end of the message buffer, too.

    I didn't see anything that looked like that crash in the crashreporter from around that time. And it looks like you're posting from IPv6 since SMF won't show me the post address.

    Did you happen to keep any more of that crash report? Or you can PM me with the IPv4 and IPv6 address it might have been submitted from so I can find it easier.

  • There was nothing else of note before that. Just a few lines from packages upgrading after the pfSense upgrade from earlier RC. But those happened many hours before this crash showed up in the web GUI. Check PM for IP Subnet.

  • Rebel Alliance Developer Netgate

    Looks somewhat familiar, might be https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903

    That isn't officially marked as fixed, though if you see that crash frequently you may want to move up to 2.4.1 snapshots and see if it's stable on a FreeBSD 11.1 base