Re: 2.6.24-rt1 IRQ routing anomaly
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Date: Thu, 21 Feb 2008 10:08:14 -0500 (EST)
On Thu, 21 Feb 2008, Mark Hounschell wrote:
To prove this is the problem, boot with noapic in the kernel command line.
1) the problem should disappear.
2) (I'm betting) you see that the eth and EMU10K1 share the same
interrupt line.
Yep, you were right. They do share the same IRQ and the problem does go away.
Unfortunately I can't run this machine with noapic. I need irq affinity.
Thanks for verifying. OK, I'll see if I can get the workaround on i386. I
thought I saw a patch someplace where someone ported that workaround. I'm
still sorting out bugs in -rt2 (why it is still not out). I'll see if I
can find time to get the workaround to i386 for -rt2 as well.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.6.24-rt1 IRQ routing anomaly
- From: Mark Hounschell
- Re: 2.6.24-rt1 IRQ routing anomaly
- References:
- 2.6.24-rt1 IRQ routing anomaly
- From: Mark Hounschell
- Re: 2.6.24-rt1 IRQ routing anomaly
- From: Steven Rostedt
- Re: 2.6.24-rt1 IRQ routing anomaly
- From: Mark Hounschell
- 2.6.24-rt1 IRQ routing anomaly
- Prev by Date: Re: [PATCH] macb: Fix speed setting
- Next by Date: Re: [PATCH 00/37] Permit filesystem local caching
- Previous by thread: Re: 2.6.24-rt1 IRQ routing anomaly
- Next by thread: Re: 2.6.24-rt1 IRQ routing anomaly
- Index(es):
Relevant Pages
|