All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Dave Jones <davej@redhat.com>, Borislav Petkov <bp@amd64.org>,
	x86@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: BAD APICID ?
Date: Mon, 7 Nov 2011 12:17:14 -0800	[thread overview]
Message-ID: <20111107201714.GA14185@suse.de> (raw)
In-Reply-To: <20111107180950.GA6411@redhat.com>

On Mon, Nov 07, 2011 at 01:09:50PM -0500, Dave Jones wrote:
> On Mon, Nov 07, 2011 at 06:54:02PM +0100, Borislav Petkov wrote:
>  > On Mon, Nov 07, 2011 at 12:39:48PM -0500, Dave Jones wrote:
>  > > We got a report from a Fedora user hitting a WARN_ON in the apic setup code.
>  > > 
>  > > Here..
>  > > 
>  > > 1230 #ifdef CONFIG_X86_32
>  > > 1231         /*
>  > > 1232          * APIC LDR is initialized.  If logical_apicid mapping was
>  > > 1233          * initialized during get_smp_config(), make sure it matches the
>  > > 1234          * actual value.
>  > > 1235          */
>  > > 1236         i = early_per_cpu(x86_cpu_to_logical_apicid, cpu);
>  > > 1237         WARN_ON(i != BAD_APICID && i != logical_smp_processor_id());
>  > > 1238         /* always use the value from LDR */
>  > > 1239         early_per_cpu(x86_cpu_to_logical_apicid, cpu) =
>  > > 1240                 logical_smp_processor_id();
>  > > 
>  > > The full report is at https://bugzilla.redhat.com/show_bug.cgi?id=743930
>  > > 
>  > > Report is against our 3.0 builds, but that code look unchanged in 3.1 too,
>  > > and even in current Linus head.
>  > > 
>  > > Any thoughts on what could cause this ?
>  > 
>  > Already fixed upstream: 838312be46f3abfbdc175f81c3e54a857994476d
>  > 
>  > Here's the whole thread: http://lkml.org/lkml/2011/10/14/231
>  > 
>  > HTH.
> 
> ah, excellent, thanks.
> That seems to have not hit stable, even though it was cc'd. Greg ?

It's already been queued up for the next stable release, which should be
coming out later this week once the firehose of the 3.2 merge window
slows down.

thanks,

greg k-h

      reply	other threads:[~2011-11-07 20:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 17:39 BAD APICID ? Dave Jones
2011-11-07 17:54 ` Borislav Petkov
2011-11-07 18:09   ` Dave Jones
2011-11-07 20:17     ` Greg KH [this message]

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=20111107201714.GA14185@suse.de \
    --to=gregkh@suse.de \
    --cc=bp@amd64.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.