[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51368692.4090204@linux.intel.com>
Date: Tue, 05 Mar 2013 15:58:10 -0800
From: "H. Peter Anvin" <hpa@...ux.intel.com>
To: Dave Hansen <dave@...ux.vnet.ibm.com>
CC: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>, bp@...en8.de,
linux-kernel@...r.kernel.org, "Yu, Fenghua" <fenghua.yu@...el.com>
Subject: Re: [3.9-rc1 x86] Bug in ioremap code?
Fenghua,
Could you look at this thread and see if you can see what the problem is?
-hpa
On 03/05/2013 03:46 PM, Dave Hansen wrote:
> 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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists