From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
rrl125@gmail.com, fa.linux.kernel@googlegroups.com,
"Berck E. Nash" <flyboy@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: x2apic boot failure on recent sandy bridge system
Date: Fri, 19 Oct 2012 16:36:52 -0700 [thread overview]
Message-ID: <5081E414.6080004@zytor.com> (raw)
In-Reply-To: <CAE9FiQUmTnhCzvaxaHbwWbcxDrjYix91Yf8TZN6ob0W_Yz1csQ@mail.gmail.com>
On 10/19/2012 04:32 PM, Yinghai Lu wrote:
> On Fri, Oct 19, 2012 at 4:03 PM, Suresh Siddha
> <suresh.b.siddha@intel.com> wrote:
>> On Fri, 2012-10-19 at 13:42 -0700, rrl125@gmail.com wrote:
>>> Any update? The messages just seem to have stopped months ago. A
>>> fallback would be nice, I have been booting the kernel with noa2xpic
>>> for since kernel 3.2, and currently I am working with 3.6.2.
>>>
>>> If needed I can try to attempt modifying the patch to include
>>> fallback, but I am probably not the best person to do it.
>>>
>>
>> Are you referring to this commit that made into the mainline tree
>> already?
>>
>> commit fb209bd891645bb87b9618b724f0b4928e0df3de
>> Author: Yinghai Lu <yinghai@kernel.org>
>> Date: Wed Dec 21 17:45:17 2011 -0800
>>
>> x86, x2apic: Fallback to xapic when BIOS doesn't setup interrupt-remapping
>
> I think his system has DMAR table and cpu support x2apic, So kernel
> will switch to x2apic,
>
> but somehow BIOS SMI handler has problem with x2apic. should be thinkpad W520?
>
Right, StinkPad W520 needs a quirk.
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-10-19 23:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.1zfuXwqYK6u81uBoo3IdpawcpWw@ifi.uio.no>
[not found] ` <fa.p3cpkKIGUNv0/iot3o7KT9bb98M@ifi.uio.no>
[not found] ` <fa.iPHW7usT23k+cCA19L3eXEDu91Q@ifi.uio.no>
[not found] ` <fa.7eOK+XcsKUWU4ZXhBj2K6znxrvc@ifi.uio.no>
[not found] ` <fa.VGxfKOh1Z07X1TXm5PxMIlV4xu8@ifi.uio.no>
[not found] ` <fa.eH+BpYDdp4xIWE4V+wJu6hFrVxM@ifi.uio.no>
2012-10-19 20:42 ` x2apic boot failure on recent sandy bridge system rrl125
2012-10-19 23:03 ` Suresh Siddha
2012-10-19 23:32 ` Yinghai Lu
2012-10-19 23:36 ` H. Peter Anvin [this message]
2012-10-20 0:02 ` Suresh Siddha
2012-10-20 0:41 ` Yinghai Lu
2011-12-10 1:56 Berck E. Nash
2011-12-10 20:17 ` Yinghai Lu
2011-12-10 22:58 ` Berck E. Nash
2011-12-10 23:11 ` Yinghai Lu
2011-12-11 7:57 ` Ingo Molnar
2011-12-11 21:43 ` Yinghai Lu
2011-12-11 22:05 ` Berck E. Nash
2011-12-12 3:40 ` Yinghai Lu
2011-12-12 23:21 ` Berck E. Nash
2011-12-13 0:25 ` Suresh Siddha
2011-12-13 1:29 ` Yinghai Lu
2011-12-13 1:41 ` Suresh Siddha
2011-12-13 4:32 ` Yinghai Lu
2011-12-13 5:13 ` Yinghai Lu
2011-12-16 13:59 ` Berck E. Nash
2011-12-18 8:47 ` Ingo Molnar
2011-12-12 23:42 ` H. Peter Anvin
2011-12-13 1:25 ` Yinghai Lu
2011-12-12 7:23 ` Suresh Siddha
-- strict thread matches above, loose matches on Subject: below --
2011-12-10 1:46 Berck E. Nash
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=5081E414.6080004@zytor.com \
--to=hpa@zytor.com \
--cc=fa.linux.kernel@googlegroups.com \
--cc=flyboy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rrl125@gmail.com \
--cc=suresh.b.siddha@intel.com \
--cc=yinghai@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.