From: Jim Paris <jim@jtan.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCI IRQ problems: "nobody cared!"
Date: Fri, 15 Oct 2004 14:51:07 -0400 [thread overview]
Message-ID: <20041015185107.GA1828@jim.sh> (raw)
In-Reply-To: <1097846385.9857.18.camel@localhost.localdomain>
> I posted a patch to poll when we find IRQ's have gone astray. It needs
> redoing versus Ingo's new 2.6.9 IRQ code but should apply cleanly to
> 2.6.8. You can the boot with "irqpoll" as a boot option and the box
> should survive.
You rock! irqpoll works like a charm. I get the same error in the
same place, but now all of my devices still work. I don't see any
obvious performance impact (although I haven't tested it much).
I applied this irqpoll patch:
http://groups.google.com/groups?selm=2BunT-6Be-15%40gated-at.bofh.it
and then some minor fixes (see below).
The log for this boot are at
https://jim.sh/svn/jim/devl/toughbook/log/irqpoll.txt
in case anyone is interested.
-jim
diff -urN ac/arch/i386/kernel/irq.c jim/arch/i386/kernel/irq.c
--- ac/arch/i386/kernel/irq.c 2004-10-15 13:18:46.000000000 -0400
+++ jim/arch/i386/kernel/irq.c 2004-10-15 13:18:26.000000000 -0400
@@ -391,11 +391,11 @@
{
if((irqfixup == 2 && irq == 0) || action_ret == IRQ_NONE)
{
+ int ok;
#ifdef CONFIG_4KSTACKS
u32 *isp;
union irq_ctx * curctx;
union irq_ctx * irqctx;
- int ok;
curctx = (union irq_ctx *) current_thread_info();
irqctx = hardirq_ctx[smp_processor_id()];
@@ -435,7 +435,7 @@
#else
spin_unlock(&desc->lock);
- ok = misrouted_irq(irq, desc, regs);
+ ok = misrouted_irq(irq, regs);
spin_lock(&desc->lock);
#endif
next prev parent reply other threads:[~2004-10-15 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 8:37 PCI IRQ problems: "nobody cared!" Jim Paris
2004-10-15 13:19 ` Alan Cox
2004-10-15 18:51 ` Jim Paris [this message]
2004-10-16 5:55 ` Len Brown
2004-10-17 0:12 ` Jim Paris
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=20041015185107.GA1828@jim.sh \
--to=jim@jtan.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.