All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <andi@firstfloor.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] [arch-x86] Allow SRAT integrity check to be skipped
Date: Tue, 07 Sep 2010 12:38:57 -0700	[thread overview]
Message-ID: <1283888337.18468.9.camel@pjaxe> (raw)
In-Reply-To: <20100903063934.GA25863@elte.hu>

On Thu, 2010-09-02 at 23:39 -0700, Ingo Molnar wrote:
> * Andi Kleen <andi@firstfloor.org> wrote:
> 
> > > This isnt a particularly useful solution to users of said systems - 
> > > they have to figure out that this option exists, and then they have 
> > > to enter this option on the boot line.
> > 
> > This usually only happens in early preproduction systems. So far the 
> > BIOS always got fixed before they shipped to users.
> 
> 'Usually' != 'always'. Read the changelog:
> 
>   ' There are BIOSes in production that have these failures, so this will 
>     allow people in the field to work around these BIOS issues. '
> 
> Peter, which system in production that has this problem? That one needs 
> a DMI match.

It's one SKU of a Nehalem-EX system.  The BIOS for that SKU has an issue
with resolving SRAT hotplug enumeration, and screws up the table.  Other
SKU's of this same platform do not have the issue.  Efforts are underway
to get this BIOS fixed, but in the meantime, there's nothing for users
to work around the bug (aside from disabling memory hotplug in the
BIOS).  Another platform almost shipped with the same symptoms, but
caught it and had it fixed before it shipped (didn't catch it early
because Windows wasn't failing, and most of the testing on that platform
was done under Windows).

I agree with Andi that adding DMI strings would be overkill and would
leave clutter once the BIOS is fixed.  I look at this patch as a
stop-gap measure for people to fall back on until a newer BIOS is
available to correct the NUMA enumeration issues.  Without it, we have
nothing to point users to when they run into this, waiting for a new
BIOS.

Cheers,
-PJ


  reply	other threads:[~2010-09-07 19:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01 21:33 [PATCH] [arch-x86] Allow SRAT integrity check to be skipped Peter P Waskiewicz Jr
2010-09-01 21:33 ` Andi Kleen
2010-09-01 22:04 ` rdunlap
2010-09-01 22:11   ` Peter P Waskiewicz Jr
2010-09-08 19:09     ` H. Peter Anvin
2010-09-03 10:04   ` Andi Kleen
2010-09-02  6:57 ` Ingo Molnar
2010-09-02 10:03   ` Andi Kleen
2010-09-03  6:39     ` Ingo Molnar
2010-09-07 19:38       ` Peter P Waskiewicz Jr [this message]
2010-09-07 19:56         ` Ingo Molnar
2010-09-07 20:03         ` H. Peter Anvin
2010-09-07 20:16           ` Peter P Waskiewicz Jr
2010-09-07 20:48             ` H. Peter Anvin
2010-09-08  6:55           ` Andi Kleen
2010-09-08 18:03             ` H. Peter Anvin
2010-09-08 18:51               ` Peter P Waskiewicz Jr

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=1283888337.18468.9.camel@pjaxe \
    --to=peter.p.waskiewicz.jr@intel.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.