[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130320171449.GB23362@digium.com>
Date: Wed, 20 Mar 2013 12:14:49 -0500
From: Shaun Ruffell <sruffell@...ium.com>
To: "Yu, Fenghua" <fenghua.yu@...el.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?
On Wed, Mar 20, 2013 at 05:05:40PM +0000, Yu, Fenghua wrote:
> From: Shaun Ruffell [mailto:sruffell@...ium.com]
> >
> > 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?
Attached.
--
Shaun Ruffell
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: www.digium.com & www.asterisk.org
View attachment "config" of type "text/plain" (79787 bytes)
Powered by blists - more mailing lists