[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQUmTnhCzvaxaHbwWbcxDrjYix91Yf8TZN6ob0W_Yz1csQ@mail.gmail.com>
Date: Fri, 19 Oct 2012 16:32:38 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: rrl125@...il.com, fa.linux.kernel@...glegroups.com,
"Berck E. Nash" <flyboy@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: x2apic boot failure on recent sandy bridge system
On Fri, Oct 19, 2012 at 4:03 PM, Suresh Siddha
<suresh.b.siddha@...el.com> wrote:
> On Fri, 2012-10-19 at 13:42 -0700, rrl125@...il.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@...nel.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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists