From: Borislav Petkov <bp@amd64.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org, Borislav Petkov <bp@amd64.org>
Subject: Re: linux-next: Tree for Feb 1 (mce_amd.c)
Date: Thu, 2 Feb 2012 15:26:28 +0100 [thread overview]
Message-ID: <20120202142628.GA1052@aftab> (raw)
In-Reply-To: <4F298A6C.6010101@xenotime.net>
On Wed, Feb 01, 2012 at 10:54:36AM -0800, Randy Dunlap wrote:
> On 01/31/2012 10:16 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20120131:
>
>
> mce_amd.c:(.cpuinit.text+0x4723): undefined reference to `cpu_llc_shared_map'
Yeah, -rc2 has that problem too with your randconfig. The issue is with
CONFIG_SMP not being set.
The following chunk should cure it:
--
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 5bed94e..63fcb8a 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -897,7 +897,7 @@ config X86_MCE_INTEL
config X86_MCE_AMD
def_bool y
prompt "AMD MCE features"
- depends on X86_MCE && X86_LOCAL_APIC
+ depends on X86_MCE && X86_LOCAL_APIC && SMP
---help---
Additional support for AMD specific MCE features such as
the DRAM Error Threshold.
--
Thanks.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-02-02 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:16 linux-next: Tree for Feb 1 Stephen Rothwell
2012-02-01 18:51 ` linux-next: Tree for Feb 1 (media/dvb/dm1105) Randy Dunlap
2012-02-01 18:54 ` linux-next: Tree for Feb 1 (mce_amd.c) Randy Dunlap
2012-02-02 14:26 ` Borislav Petkov [this message]
2012-02-02 17:53 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120202142628.GA1052@aftab \
--to=bp@amd64.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.