kernel panic while detecting cpu in FreeBSD 9

Konstantin Belousov kostikbel at gmail.com
Wed Apr 18 10:34:21 UTC 2012


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


More information about the freebsd-stable mailing list