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

Steven Rostedt wrote:
> On Sun, 2 Mar 2008, Jon Masters wrote:
>> On Thu, 2008-02-21 at 10:08 -0500, 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.
>> What's the situation with this one? Want me to look at it?
> 
> Jon,
> 
> The board Mark has may just be some cheap hardware. It would be great
> that RT would work on all boxes, but I'm not sure we want to spend time on
> "broken-by-design" hardware while there's bigger fish in the sea to catch.
> 
> The current workaround is just use noapic, although I do understand
> that's not good enough for Mark. But I'm sure Mark has other hardware
> he could use ;-)
> 
> -- Steve
> 
> 
Steve is correct. I have plenty of other choices. Steve, you mentioned, a "work around"
is in -rt3. My only concern is does the current "work around" for other hardware really 
work or may I see this again with other "non cheap" hardware? 

Is there a known list of hardware this problem is seen on?

Thanks
Mark

  reply	other threads:[~2008-03-03 13:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 12:01 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
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 [this message]
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=47CBFED1.7090903@compro.net \
    --to=markh@compro.net \
    --cc=dmarkh@cfl.rr.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®