Re: [PATCH 3/3] x86: when acpi_noirq is set, use mptable instead of MADT

"acpi=noirq" and "pci=noacpi" are not reliable in IOAPIC mode --
as, by definition, they skip the processing of the ACPI interrupt itself.
On some systems this happens to work, and on some systems it doesn't --
depends on if there was an override for the SCI or if it appears as
a standard PCI interrupt.

So the bigger question is why you need these workarounds in the first place.

-Len



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 3/3] x86: when acpi_noirq is set, use mptable instead of MADT
    • From: "Yinghai Lu" <[email protected]>
  • Re: [PATCH 3/3] x86: when acpi_noirq is set, use mptable instead of MADT
    • From: "Yinghai Lu" <[email protected]>

• References:
  • [PATCH 3/3] x86: when acpi_noirq is set, use mptable instead of MADT
    • From: "Yinghai Lu" <[email protected]>

• Prev by Date: [PATCH] synclink_gt: fix init error handling
• Next by Date: Forgotten patch to fs/locks.c
• Previous by thread: Re: [PATCH 3/3] x86: when acpi_noirq is set, use mptable instead of MADT
• Next by thread: Re: [PATCH 3/3] x86: when acpi_noirq is set, use mptable instead of MADT
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]