Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756439Ab2HGU4x (ORCPT ); Tue, 7 Aug 2012 16:56:53 -0400 Received: from mga02.intel.com ([134.134.136.20]:65277 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756303Ab2HGU4v (ORCPT ); Tue, 7 Aug 2012 16:56:51 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,352,1309762800"; d="scan'208";a="177153963" Subject: Re: IRQ remapping problem on Macbook Air 5,1 From: Suresh Siddha Reply-To: Suresh Siddha To: Seth Forshee Cc: Joerg Roedel , linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Len Brown , Joerg Roedel , Yinghai Lu Date: Tue, 07 Aug 2012 13:53:33 -0700 In-Reply-To: <20120807205519.GC23829@thinkpad-t410> References: <20120807194837.GB23829@thinkpad-t410> <20120807201030.GJ1917@8bytes.org> <1344372472.27383.8.camel@sbsiddha-desk.sc.intel.com> <20120807205519.GC23829@thinkpad-t410> Organization: Intel Corp Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.0.3 (3.0.3-1.fc15) Content-Transfer-Encoding: 7bit Message-ID: <1344372814.27383.12.camel@sbsiddha-desk.sc.intel.com> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1634 Lines: 39 On Tue, 2012-08-07 at 15:55 -0500, Seth Forshee wrote: > On Tue, Aug 07, 2012 at 01:47:52PM -0700, Suresh Siddha wrote: > > On Tue, 2012-08-07 at 22:10 +0200, Joerg Roedel wrote: > > > Hi Seth, > > > > > > On Tue, Aug 07, 2012 at 02:48:37PM -0500, Seth Forshee wrote: > > > > This machine has a bug in its ACPI tables that's causing it to fail to > > > > boot unless intremap=off is passed to the kernel. The MADT defines a > > > > single IOAPIC with id 2, but the remapping unit defined in DMAR matches > > > > id 0. Thus interrupt remapping fails, and the kernel panics with the > > > > message "timer doesn't work through Interrupt-remapped IO-APIC." If I > > > > force the use of the non-matching ir hardware for the IOAPIC everything > > > > seems to works fine. dmesg for the working boot is below. > > > > > > There are AMD systems with similar problems. For example I had a system > > > with 2 IO-APICs but only one was described in the IOMMU ACPI table. > > > > This issue should be caught by the current check in > > parse_ioapics_under_ir() > > > > if (ir_supported && ir_ioapic_num != nr_ioapics) { > > ... > > No, there's one IOMMU and one IOAPIC, so this check doesn't catch it. > The problem is that the ids in the ACPI tables for the devices don't > match. > Seth, I am referring to the issue that Joerg raised. Not referring to your current issue. thanks, suresh -- 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/