From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: mingo@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: 2.6.10 - Misrouted IRQ recovery for review
Date: Sun, 02 Jan 2005 15:18:19 +0000 [thread overview]
Message-ID: <1104679098.14712.68.camel@localhost.localdomain> (raw)
In-Reply-To: <41D70AF4.7030901@tmr.com>
> I saw this message coming out of ac2 with my runaway IRQ 18 problem, so
> I tried irqpoll, and it just "went away" beyond sysreq or other gentle
> recovery.
That means that the cause of the IRQ that hung your machine was not one
we had any driver for. Thats generally BIOS bogosities on a large scale.
The irqpoll code can recover from cases where an IRQ turns up on the
wrong IRQ line but for a registered driver and when an IRQ fails to turn
up in which case the timer tick picks it up on x86 (which may or may not
make it "useful").
> I suspect that the problem lies in sharing the shared IRQ, and that
> polling doesn't solve the problem, just changes it to a hang witing for
> the misrouted IRQ. Still poking for the real cause, no patch or
> anything, but acpi={off,ht}, noapic, pci=routeirq, etc have no benefit
> (for me).
That wouldn't really fit how the hardware works. You appear to have some
unsupported device connected to that line and asserting IRQ right from
boot.
Alan
next prev parent reply other threads:[~2005-01-02 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 15:58 PATCH: 2.6.10 - Misrouted IRQ recovery for review Alan Cox
2004-12-28 17:11 ` Arjan van de Ven
2004-12-28 16:37 ` Alan Cox
2004-12-28 17:28 ` Dmitry Torokhov
2004-12-28 18:25 ` David S. Miller
2004-12-28 18:50 ` Dmitry Torokhov
2004-12-28 18:53 ` David S. Miller
2004-12-28 19:21 ` Dmitry Torokhov
2004-12-28 19:26 ` David S. Miller
2004-12-29 13:57 ` Ingo Molnar
2005-01-01 17:59 ` Pavel Machek
2005-01-01 20:41 ` Bill Davidsen
2005-01-02 15:18 ` Alan Cox [this message]
2005-01-02 17:47 ` Bill Davidsen
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=1104679098.14712.68.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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).