[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090112113720.GB21051@elte.hu>
Date: Mon, 12 Jan 2009 12:37:20 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Stefan Assmann <sassmann@...e.de>
Cc: Len Brown <lenb@...nel.org>, Bjorn Helgaas <bjorn.helgaas@...com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Olaf Dabrunz <od@...e.de>,
Thomas Gleixner <tglx@...utronix.de>,
Steven Rostedt <rostedt@...dmis.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-acpi@...r.kernel.org, Sven Dietrich <sdietrich@...ell.com>
Subject: Re: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot
interrupt equivalent
* Stefan Assmann <sassmann@...e.de> wrote:
> Why can these IRQ lines be brought down by Boot Interrupts? Because
> there's no handler installed on the primary IO-APIC IRQ line that can
> take care of them and after too many unhandled IRQs the line will be
> shut down by the kernel.
The failure mode can be quite nasty: ranging from non-working USB (and
other) devices to hard lockups due to screaming IRQs.
Ingo
--
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