From: Tim Bird <tim.bird@am.sony.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
dirk.behme@googlemail.com,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Need help debugging RT-preempt patch
Date: Mon, 07 May 2007 14:02:51 -0700 [thread overview]
Message-ID: <463F93FB.1000908@am.sony.com> (raw)
In-Reply-To: <1178569719.3164.6.camel@imap.mvista.com>
Daniel Walker wrote:
> Are you sure you don't have HardIRQS in Threads enabled? Also are you
> sure the kernel boots without the rt patch applied.
Yes on both counts. I double-checked the configs. I'm using quilt
and the RT patch is at the end of my series, so it was easy to
pop the patch and try again (module .config fixups).
I may take a few more blind stabs at different configs before
I go diving into the networking code trying to trace something.
(or before starting to bisect the patch). Bisecting the patch
will be a bit painful since it's currently an all-in-one.
>
> ARM is supported, but specific boards are hit or miss..
>
> I've had OMAP working _in the past_ with this patch applied,
>
> http://lkml.org/lkml/2006/12/10/59
>
> There was also a patch released on one of the OMAP lists a while back
> from Dirk Behme to get OMAP working on a mor recent rt release..
OK. This is REALLY helpful info. I'll take a look.
Thanks very much!!
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================
next prev parent reply other threads:[~2007-05-07 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 18:47 Need help debugging RT-preempt patch Tim Bird
2007-05-07 20:28 ` Daniel Walker
2007-05-07 21:02 ` Tim Bird [this message]
2007-05-07 21:11 ` Daniel Walker
2007-05-08 0:20 ` john cooper
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=463F93FB.1000908@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=dirk.behme@googlemail.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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