Messages in this thread | | | Subject | Re: RT : 2.6.12rc5 + realtime-preempt-2.6.12-rc5-V0.7.47-15 | From | "Serge Noiraud" <> | Date | Wed, 01 Jun 2005 14:02:56 +0200 |
| |
Le mer 01/06/2005 à 10:23, Ingo Molnar a écrit : > * 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 Already in the config. I have the following too : CONFIG_CRITICAL_TIMING=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. The max latency reported are normal.
I have the problem with another program which mesure latencies about semaphore only in X environment too.
I tried to ssh this machine from another X environment and the problem does not exist. It's only on the console. > > Ingo [unhandled content-type:application/x-bzip][unhandled content-type:application/x-bzip] | |