[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C7122055947296@ORSMSX105.amr.corp.intel.com>
Date: Wed, 20 Mar 2013 17:05:40 +0000
From: "Yu, Fenghua" <fenghua.yu@...el.com>
To: Shaun Ruffell <sruffell@...ium.com>
CC: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
"dave@...ux.vnet.ibm.com" <dave@...ux.vnet.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [3.9-rc1] Bug in bootup code or debug code?
> From: Shaun Ruffell [mailto:sruffell@...ium.com]
> On Wed, Mar 20, 2013 at 04:32:14PM +0000, Yu, Fenghua wrote:
> > > From: Shaun Ruffell [mailto:sruffell@...ium.com]
> > > On Tue, Mar 19, 2013 at 10:12:39PM +0000, Yu, Fenghua wrote:
> > > > > From: Tetsuo Handa [mailto:penguin-kernel@...ove.SAKURA.ne.jp]
> > > > > H. Peter Anvin wrote:
> Thanks for the link. That patch applied on 3.9-rc3 did allow me to boot
> with my
> default kernel config.
Great!
>
> Not related to this patch, and not sure it really matters, but FYI: I
> just
> noticed the following warning when building the patched kernel:
>
> WARNING: vmlinux.o(.text+0x2a1a7): Section mismatch in reference from
> the function apply_microcode_early() to the
> function .cpuinit.text:print_ucode()
> The function apply_microcode_early() references
> the function __cpuinit print_ucode().
> This is often because apply_microcode_early lacks a __cpuinit
> annotation or the annotation of print_ucode is wrong.
Could you please send your .config to me?
Thanks.
-Fenghua
--
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