From: Ingo Molnar <mingo@elte.hu>
To: Serge Noiraud <serge.noiraud@bull.net>
Cc: Lee Revell <rlrevell@joe-job.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: RT : 2.6.12rc5 + realtime-preempt-2.6.12-rc5-V0.7.47-15
Date: Wed, 1 Jun 2005 10:23:51 +0200 [thread overview]
Message-ID: <20050601082351.GA30690@elte.hu> (raw)
In-Reply-To: <1117613246.5580.70.camel@ibiza.btsn.frna.bull.fr>
* Serge Noiraud <serge.noiraud@bull.net> wrote:
> Le mar 31/05/2005 à 21:47, Lee Revell a écrit :
> > On Tue, 2005-05-31 at 16:53 +0200, Serge Noiraud wrote:
> > > I have a test program which made a loop in RT to mesure the system
> > > perturbation.
> > > It works finely in a tty environment.
> > > When I run it in an X environment ( xterm ), I get something like if I
> > > click the Enter key in the active window.
> > > If I open a new xterm, this is the new active window which receive these
> > > events.
> > > These events stop when the program stop.
> > >
> > > I tried with X in RT and no RT : I have the problem.
> >
> > Try adding:
> >
> > Option "NoAccel"
> Same problem.
could you enable latency timing and tracing in the .config:
CONFIG_CRITICAL_PREEMPT_TIMING=y
CONFIG_CRITICAL_IRQSOFF_TIMING=y
CONFIG_LATENCY_TIMING=y
CONFIG_LATENCY_TRACE=y
and start a new search for a maximum latency via:
echo 0 > /proc/sys/kernel/preempt_max_latency
and then do the X test - what is the largest latency reported in
'dmesg'? Also, please send me a (bzip2 -9 compressed, if too large)
/proc/latency_trace trace output of the largest incident.
Ingo
next prev parent reply other threads:[~2005-06-01 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 14:53 RT : 2.6.12rc5 + realtime-preempt-2.6.12-rc5-V0.7.47-15 Serge Noiraud
2005-05-31 19:47 ` Lee Revell
2005-06-01 8:07 ` Serge Noiraud
2005-06-01 8:23 ` Ingo Molnar [this message]
2005-06-01 12:02 ` Serge Noiraud
2005-06-01 13:09 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 12:12 Serge Noiraud
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=20050601082351.GA30690@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=serge.noiraud@bull.net \
/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