linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Seth Forshee <seth.forshee@canonical.com>,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Len Brown <lenb@kernel.org>, Joerg Roedel <joerg.roedel@amd.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: IRQ remapping problem on Macbook Air 5,1
Date: Tue, 7 Aug 2012 22:10:30 +0200	[thread overview]
Message-ID: <20120807201030.GJ1917@8bytes.org> (raw)
In-Reply-To: <20120807194837.GB23829@thinkpad-t410>

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.

> I'm looking at how to make this machine able to boot by default. OS X
> obviously boots, and Windows presumably boots as well since Apple
> officially supports running Windows on its hardware.

These operating systems probably don't support interrupt remapping, or
the IOMMU at all.

> I've got a patch to leave IRQ remapping disabled whenever any IOAPIC
> does not have a matching ir hardware unit. This gets it to boot, but I
> thought I'd check and see whether anyone had any better ideas for how to
> fix this.

This is exactly how I fixed this issue on the AMD side too. Mind to
submit the patch?


Thanks,

	Joerg

  reply	other threads:[~2012-08-07 20:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 19:48 IRQ remapping problem on Macbook Air 5,1 Seth Forshee
2012-08-07 20:10 ` Joerg Roedel [this message]
2012-08-07 20:47   ` Suresh Siddha
2012-08-07 20:55     ` Seth Forshee
2012-08-07 20:53       ` Suresh Siddha
2012-08-07 20:48   ` [PATCH] irq_remap: disable IRQ remapping if any IOAPIC lacks an IOMMU Seth Forshee
2012-08-07 20:50     ` Suresh Siddha
2012-08-07 21:04     ` Joerg Roedel
2012-08-07 21:39       ` [PATCH v2] " Seth Forshee
2012-08-07 22:04         ` Yinghai Lu
2012-08-08 13:27           ` [PATCH v3] " Seth Forshee
2012-08-08 17:57             ` Yinghai Lu
2012-08-08 21:33               ` Seth Forshee
2012-08-10  9:32             ` Joerg Roedel

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=20120807201030.GJ1917@8bytes.org \
    --to=joro@8bytes.org \
    --cc=hpa@zytor.com \
    --cc=joerg.roedel@amd.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=seth.forshee@canonical.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).