911d6f6932
After power-on, both LAPIC and I/O APIC appear with the same APIC ID zero, which creates an ID conflict. When generating MP table, U-Boot reports zero as the LAPIC ID in the processor entry, and zero as the I/O APIC ID in the I/O APIC as well as the I/O interrupt assignment entries. Such MP table confuses Linux kernel and finally a kernel panic is seen during boot: BUG: unable to handle kernel paging request at ffff9000 IP: [<c101d462>] native_io_apic_write+0x22/0x30 *pdpt = 00000000014fb001 *pde = 00000000014ff067 *pte = 0000000000000000 Oops: 0002 [#1] Modules linked in: Pid: 1, comm: swapper Tainted: G W 3.8.7 #3 intel galileo/galileo EIP: 0060:[<c101d462>] EFLAGS: 00010086 CPU: 0 EIP is at native_io_apic_write+0x22/0x30 ... Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org> |
||
---|---|---|
.. | ||
baytrail | ||
broadwell | ||
coreboot | ||
efi | ||
intel_common | ||
ivybridge | ||
qemu | ||
quark | ||
queensbay | ||
call32.S | ||
call64.S | ||
config.mk | ||
cpu_x86.c | ||
cpu.c | ||
interrupts.c | ||
ioapic.c | ||
irq.c | ||
lapic.c | ||
Makefile | ||
mp_init.c | ||
mtrr.c | ||
pci.c | ||
resetvec.S | ||
sipi_vector.S | ||
start16.S | ||
start.S | ||
turbo.c | ||
u-boot.lds |