Hello,
I posted to the FreeBSD forum and was told to seek help on the stable
mailing list. I recently build a new system and attempted to install
FreeBSD 9 amd64 using the dvd. Shortly after the boot loader menu while
the kernel attempts to detect the processor cores I receive a kernel
trap 12 error. Kernel trap messages begin scrolling non stop but I was
able to get a picture when they paused and here is the text:
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x18
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff80823368
stack pointer = 0x28:0xffffffff811a5030
frame pointer = 0x28:0xffffffff811a5070
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 = 0 ()
trap number = 12
panic: page fault
cpuid = 0
The first suggestion from a forum poster was bad memory but I swapped
out the memory and still received the panics. Also tested the memory
with memtest86+ and the bios memory test feature. Both reported no
errors. I finally was able to get it to boot and install by breaking to
the loader prompt and typing "kern.smp.disabled=1". But the installed
system also panics at the same point during boot and the only way to get
it to boot is by disabling smp at the loader prompt.
I recompiled the kernel with "options DDB" and and tried tracing the
problem, but since it happens so soon into the boot process I cannot get
a crash dump. Here is some of my system hardware if that helps as well:
MSI P67A-GD65 (B3) mainboard
intel core i5-2500K (quad core)
G.SKILL Ripjaws X Series 8GB (2 x 4GB) DDR3 1600
My original FreeBSD forum post is at:
http://forums.freebsd.org/showthread.php?t=31156 if that helps as well.
The last forum poster suggest the problem might be in
sys/amd64/amd64/mp_machdep.c and redirected me here.
Thanks for any assistance,
-Chad
On Apr 18, 2012 2:23 AM, "Chad C" <chad@psys.us> wrote:> > The first suggestion from a forum poster was bad memory but I swapped outthe memory and still received the panics. Also tested the memory with memtest86+ and the bios memory test feature. Both reported no errors. I finally was able to get it to boot and install by breaking to the loader prompt and typing "kern.smp.disabled=1". But the installed system also panics at the same point during boot and the only way to get it to boot is by disabling smp at the loader prompt.>Please update your BIOS/UEFI and try again.
On Tue, Apr 17, 2012 at 12:52:28PM -0400, Chad C wrote:> > Hello, > I posted to the FreeBSD forum and was told to seek help on the stable > mailing list. I recently build a new system and attempted to install > FreeBSD 9 amd64 using the dvd. Shortly after the boot loader menu while > the kernel attempts to detect the processor cores I receive a kernel > trap 12 error. Kernel trap messages begin scrolling non stop but I was > able to get a picture when they paused and here is the text: > > > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x18 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff80823368 > stack pointer = 0x28:0xffffffff811a5030 > frame pointer = 0x28:0xffffffff811a5070 > 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 = 0 () > trap number = 12 > panic: page fault > cpuid = 0 > > > The first suggestion from a forum poster was bad memory but I swapped > out the memory and still received the panics. Also tested the memory > with memtest86+ and the bios memory test feature. Both reported no > errors. I finally was able to get it to boot and install by breaking to > the loader prompt and typing "kern.smp.disabled=1". But the installed > system also panics at the same point during boot and the only way to get > it to boot is by disabling smp at the loader prompt. > > I recompiled the kernel with "options DDB" and and tried tracing the > problem, but since it happens so soon into the boot process I cannot get > a crash dump. Here is some of my system hardware if that helps as well: > MSI P67A-GD65 (B3) mainboard > intel core i5-2500K (quad core) > G.SKILL Ripjaws X Series 8GB (2 x 4GB) DDR3 1600ddb is not for getting crash dump, it is for backtrace. System with ddb present should print out the stack trace of the panic location. Please post this information verbatim.> > My original FreeBSD forum post is at: > http://forums.freebsd.org/showthread.php?t=31156 if that helps as well. > The last forum poster suggest the problem might be in > sys/amd64/amd64/mp_machdep.c and redirected me here. > > Thanks for any assistance, > > -Chad > > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20120417/008b920b/attachment.pgp
Updated the mainboard UEFI to latest version but am still getting the
same kernel page fault.
I compiled "options DDB" and "options GDB" into the generic
kernel.
After rebooting and entering DDB I get the following from various commands:
On bootup I am now getting the following:
real memory = 8589934592 (8192 MB)
avail memory = 8198332416 (7818 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <ALASKA A M I>
panic: AP #2 (PHY# 4) failed!
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
kdb_backtrace() at KDB_backtrace+0x37
panic() at panic+0x187
cpu_mp_start() at cpu_mp_start+0x589
mp_start() at mp_start+0x85
mi_startup() at mi_startup+0x77
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at kdb_enter+0x3b: movq $0,0x905dc2(%rip)
db>
Typing "s" and "c" at the db prompt gives the following:
db> s
[ thread pid 0 tid 0 ]
Stopped at kdb_enter+0x46: addq $0x8,%rsp
db> c
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x18
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff808316e8
stack pointer = 0x28:0xffffffff81412ab0
frame pointer = 0x28:0xffffffff81412af0
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = trace trap, resume, IOPL = 0
current process = 0 ()
[ thread pid 0 tid 0 ]
Stopped at _thread_lock_flags+0x28: movq 0x18(%r12),%rax
And trace gives me the following output:
db> trace
Tracing pid 0 tid 0 td 0xffffffff8112f830
_thread_lock_flags() at _thread_lock_flags+0x28
kern_reboot() at kern_reboot+0x33
panic() at panic+0x171
cpu_mp_start() at cpu_mp_start+0x589
mp_start() at mp_start+0x85
mi_startup() at mi_startup+0x77
btext() at btext+0x2c
-Chad
On Wed, Apr 18, 2012 at 12:24:17AM -0400, Chad C wrote:> Updated the mainboard UEFI to latest version but am still getting the > same kernel page fault. > > I compiled "options DDB" and "options GDB" into the generic kernel. > After rebooting and entering DDB I get the following from various commands: > > On bootup I am now getting the following: > > real memory = 8589934592 (8192 MB) > avail memory = 8198332416 (7818 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: <ALASKA A M I> > panic: AP #2 (PHY# 4) failed! > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > kdb_backtrace() at KDB_backtrace+0x37 > panic() at panic+0x187 > cpu_mp_start() at cpu_mp_start+0x589 > mp_start() at mp_start+0x85 > mi_startup() at mi_startup+0x77 > btext() at btext+0x2c > KDB: enter: panic > [ thread pid 0 tid 0 ] > Stopped at kdb_enter+0x3b: movq $0,0x905dc2(%rip) > db>So your other core failed to start. You might try a lack posting exact model/bios version of the machine and mainboard. But indeed, this is most often BIOS bugs. Sometimes in the strange areas like USB, e.g. SMI handler for emulating legacy PS/2 keyboard. As a shot in the dark, try to fiddle with this setting. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20120418/2015c11a/attachment.pgp