public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Bird <tim.bird@am.sony.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Need help debugging RT-preempt patch
Date: Mon, 07 May 2007 11:47:37 -0700	[thread overview]
Message-ID: <463F7449.2020509@am.sony.com> (raw)

I've applied patch-2.6.21-rt1 to a 2.6.21 kernel I'm using.
With the patch applied, but no RT-Preempt options enabled,
I'm getting network failures (eth0 transmit timeouts) on
an OMAP board.

I'm not sure what the best method is to debug this.  Should
I turn on the latency tracer?  Should I post my configuration?
Should I try to break up the patch and apply changes in small doses?
I'm not familiar with the network code, or with the RT code (yet),
so for now I'm kind of stumbling in the dark.

Note that I have other patches applied, for platform support
for the OMAP.

I believe ARM (or OMAP) is not supported by the RT-preempt patch
at the moment.  But I'd like to carry the patches in my kernel even
if the options for RT-preempt are off, because I want to experiment
with RT-preempt on other platforms (x86 and MIPS).

Any suggestions for where to start to isolate this would
be appreciated.

Thanks,
 -- Tim

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================


             reply	other threads:[~2007-05-07 19:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 18:47 Tim Bird [this message]
2007-05-07 20:28 ` Need help debugging RT-preempt patch Daniel Walker
2007-05-07 21:02   ` Tim Bird
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=463F7449.2020509@am.sony.com \
    --to=tim.bird@am.sony.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