[Bug 193011] New: kernel panic after updating to CURRENT r270648

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Aug 26 10:48:26 UTC 2014


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193011

            Bug ID: 193011
           Summary: kernel panic after updating to CURRENT r270648
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: shuriku at shurik.kiev.ua

After update from 270011 to 270648 I have kernel panic during system boot:

kernel trap 12 with interrupts disabled


Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address   = 0x1
fault code              = supervisor read instruction, page not present
instruction pointer     = 0x20:0x1
stack pointer           = 0x28:0xfffffe043ab207d0
frame pointer           = 0x28:0xfffffe043ab20810
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         = 11 (idle: cpu2)
trap number             = 12
panic: page fault
cpuid = 2
KDB: stack backtrace:
#0 0xffffffff80962a10 at kdb_backtrace+0x60
#1 0xffffffff80923741 at panic+0x1c1
#2 0xffffffff80d99e9f at trap_fatal+0x38f
#3 0xffffffff80d9a1ec at trap_pfault+0x33c
#4 0xffffffff80d9980e at trap+0x45e
#5 0xffffffff80d7bca2 at calltrap+0x8
#6 0xffffffff80d7d019 at Xrendezvous+0x89
#7 0xffffffff8036f07a at acpi_cpu_idle+0x13a
#8 0xffffffff80d8218f at cpu_idle_acpi+0x3f
#9 0xffffffff80d82230 at cpu_idle+0x90
#10 0xffffffff80952295 at sched_idletd+0x1f5
#11 0xffffffff808eb5ca at fork_exit+0x9a
#12 0xffffffff80d7c1de at fork_trampoline+0xe
Uptime: 52s
Dumping 745 out of 15926 MB:..3%..11%..22%..31%..41%..52%..61%..71%..82%..91%

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list