All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mark Hounschell <markh@compro.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Jon Masters <jonathan@jonmasters.org>
Subject: Re: 2.6.24-rt1 IRQ routing anomaly
Date: Thu, 21 Feb 2008 17:41:48 -0500	[thread overview]
Message-ID: <47BDFE2C.208@cfl.rr.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0802211005380.9890@gandalf.stny.rr.com>

Steven Rostedt wrote:
> 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

I'll be happy to test it for ya

Mark


  reply	other threads:[~2008-02-21 22:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 12:01 2.6.24-rt1 IRQ routing anomaly Mark Hounschell
2008-02-21 12:51 ` Steven Rostedt
2008-02-21 13:30   ` Mark Hounschell
2008-02-21 15:08     ` Steven Rostedt
2008-02-21 22:41       ` Mark Hounschell [this message]
2008-02-21 23:10         ` Steven Rostedt
2008-03-03  4:31       ` Jon Masters
2008-03-03 13:24         ` Steven Rostedt
2008-03-03 13:36           ` Mark Hounschell
2008-03-03 14:31             ` Steven Rostedt
2008-03-03 17:00               ` Jon Masters

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=47BDFE2C.208@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --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 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.