From: Borislav Petkov <bp@amd64.org>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Tony Luck <tony.luck@intel.com>,
Daniel J Blueman <daniel@numascale-asia.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] RAS: Numascale fix
Date: Tue, 9 Oct 2012 15:04:02 +0200 [thread overview]
Message-ID: <20121009130402.GB26450@aftab.osrc.amd.com> (raw)
Hi guys,
just a small fix for an oops on Numascale's confederate systems. It can
go in ASAP.
Thanks.
The following changes since commit 547b1e81afe3119f7daf702cc03b158495535a25:
Fix staging driver use of VM_RESERVED (2012-10-09 21:06:41 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git tags/numascale_mce_fix
for you to fetch changes up to 124556ec1555b89af76cec3e41375b6f9a557ead:
x86, AMD, MCE: Prevent oops on multi-server system (2012-10-09 14:48:43 +0200)
----------------------------------------------------------------
A fix for a bug causing an OOPS on confederate systems from Numascale
where northbridge descriptors are not unique, causing a lookup failure
of the northbridge descriptor in the amd_nb.c code.
A more general fix is in the works.
----------------------------------------------------------------
Daniel J Blueman (1):
x86, AMD, MCE: Prevent oops on multi-server system
arch/x86/kernel/cpu/mcheck/mce_amd.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
--
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 reply other threads:[~2012-10-09 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 13:04 Borislav Petkov [this message]
2012-10-17 17:05 ` H. Peter Anvin
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=20121009130402.GB26450@aftab.osrc.amd.com \
--to=bp@amd64.org \
--cc=daniel@numascale-asia.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®