From: Ingo Molnar <mingo@elte.hu>
To: Stefan Assmann <sassmann@suse.de>
Cc: Len Brown <lenb@kernel.org>, Bjorn Helgaas <bjorn.helgaas@hp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Olaf Dabrunz <od@suse.de>, Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Sven Dietrich <sdietrich@novell.com>
Subject: Re: PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent
Date: Mon, 12 Jan 2009 12:37:20 +0100 [thread overview]
Message-ID: <20090112113720.GB21051@elte.hu> (raw)
In-Reply-To: <496B24E5.1070804@suse.de>
* Stefan Assmann <sassmann@suse.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
next prev parent reply other threads:[~2009-01-12 11:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 23:03 PCI, ACPI, IRQ, IOAPIC: reroute PCI interrupt to legacy boot interrupt equivalent Len Brown
2009-01-12 11:09 ` Stefan Assmann
2009-01-12 11:37 ` Ingo Molnar [this message]
2009-01-12 18:51 ` Bjorn Helgaas
2009-01-12 19:25 ` Jon Masters
2009-01-12 19:45 ` Bjorn Helgaas
2009-01-13 13:32 ` Stefan Assmann
2009-01-13 18:22 ` Olaf Dabrunz
2009-01-15 15:34 ` Olaf Dabrunz
2009-01-12 23:36 ` Eric W. Biederman
2009-01-13 0:29 ` Jon Masters
2009-01-13 1:47 ` Ingo Molnar
2009-01-13 3:47 ` Eric W. Biederman
2009-01-13 4:26 ` Jon Masters
2009-01-14 11:40 ` Ingo Molnar
2009-01-14 19:18 ` Jon Masters
2009-01-14 22:42 ` Eric W. Biederman
2009-01-14 22:53 ` Steven Rostedt
2009-01-14 22:56 ` Jon Masters
2009-01-15 12:36 ` Olaf Dabrunz
2009-01-15 10:16 ` Stefan Assmann
2009-01-13 11:18 ` Stefan Assmann
2009-01-13 15:57 ` Olaf Dabrunz
2009-01-15 0:10 ` Bjorn Helgaas
2009-01-15 14:08 ` Stefan Assmann
2009-01-13 8:25 ` Shaohua Li
2009-01-14 9:57 ` Stefan Assmann
2009-01-14 15:48 ` Bjorn Helgaas
2009-01-14 15:55 ` Olaf Dabrunz
2009-01-14 16:52 ` Bjorn Helgaas
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=20090112113720.GB21051@elte.hu \
--to=mingo@elte.hu \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=od@suse.de \
--cc=rostedt@goodmis.org \
--cc=sassmann@suse.de \
--cc=sdietrich@novell.com \
--cc=tglx@linutronix.de \
/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