Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933009Ab2JSXcl (ORCPT ); Fri, 19 Oct 2012 19:32:41 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:34405 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932113Ab2JSXcj (ORCPT ); Fri, 19 Oct 2012 19:32:39 -0400 MIME-Version: 1.0 In-Reply-To: <1350687838.6017.10.camel@sbsiddha-desk.sc.intel.com> References: <1350687838.6017.10.camel@sbsiddha-desk.sc.intel.com> Date: Fri, 19 Oct 2012 16:32:38 -0700 X-Google-Sender-Auth: ZAQbAUM6NhtpErGU_JPo1J0m210 Message-ID: Subject: Re: x2apic boot failure on recent sandy bridge system From: Yinghai Lu To: Suresh Siddha Cc: rrl125@gmail.com, fa.linux.kernel@googlegroups.com, "Berck E. Nash" , "linux-kernel@vger.kernel.org" , "H. Peter Anvin" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1195 Lines: 29 On Fri, Oct 19, 2012 at 4:03 PM, Suresh Siddha 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 > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/