Not sure if it's related by 3.9-rc1 gets in to a reboot loop for me. I
assume it's triple-faulting. The last line on the console I see is:
[ 0.085702] SMP alternatives: lockdep: fixing up alternatives
[ 0.086859] smpboot: Booting Node 0, Processors [ 0.086859]
smpboot: Booting Node 0, Processors #1 OK
#1 OK
I bisected it down to the neighborhood of c47f39e. After that, I get
some compile errors:
> arch/x86/built-in.o: In function `generic_load_microcode':
> microcode_intel.c:(.text+0x28195): undefined reference to
> `microcode_sanity_check'
> microcode_intel.c:(.text+0x281ab): undefined reference to
> `get_matching_microcode'
Turning off CONFIG_MICROCODE:
-CONFIG_MICROCODE=y
-CONFIG_MICROCODE_INTEL=y
-# CONFIG_MICROCODE_AMD is not set
-CONFIG_MICROCODE_OLD_INTERFACE=y
-CONFIG_MICROCODE_INTEL_LIB=y
-CONFIG_MICROCODE_INTEL_EARLY=y
-CONFIG_MICROCODE_EARLY=y
+# CONFIG_MICROCODE is not set
lets it boot again and fixes those compile errors. This is with this
config:
http://i-love.sakura.ne.jp/tmp/config-3.9-rc1
running under a kvm guest:
qemu-system-x86_64 -append 'earlyprintk=ttyS0,115200,keep
console=ttyS0,115200 nmi_watchdog=0 root=/dev/sda1 bootmem_debug'
-kernel vmlinuz -usbdevice tablet -vnc :1 -net user -net
nic,model=e1000 -hda sarge-amd64-runme-1G.img -m 10240 -smp 2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
