LKML Archive on
help / color / mirror / Atom feed
From: Ingo Molnar <>
To: Kevin Winchester <>
Cc: Linux Kernel Mailing List <>,
	Arjan van de Ven <>,
	Steven Rostedt <>,
	Peter Zijlstra <>
Subject: Re: Latency issues with x86.git
Date: Thu, 14 Feb 2008 07:07:58 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

* Kevin Winchester <> wrote:

> Hi Ingo,
> I have encountered (a handful of times in the past few months) some 
> real interactivity problems on my system.  Moving the mouse or typing 
> a key on the keyboard takes around a second to show any response.  
> Once I perform a reboot, the problem is gone again.  I am currently 
> running x86.git mm branch, but I switch between that branch, mainline 
> git, and mm kernels, so I cannot guarantee on which trees I have or 
> have not seen the problem.

please try sched-devel.git, which has both the latest scheduler fixes, 
and also the new "ftrace" latency tracing framework that can be used to 
trace various latency problems. You can pick up sched-devel.git via:

firstly, there's a chance that sched-devel.git solves the problem - in 
that case please report it.

if it doesnt, then you can trace various latencies via these:


just enable them, boot into the new kernel and mount debugfs:

   mount -t debugfs nodev /debug

and then you can select one of the tracers (that have been enabled in 
the .config) via /debug/tracing/* files. The usage of these files should 
be self-explaining - if any of them wasnt then please let us know and 
we'll make the "first quick glance experience" better :)

the one interesting to you would be the "wakeup" tracer. Enable it, and 
if you echo 0 into /debug/tracing/tracing_max_latency it starts tracking 
the worst-case delay experienced on your system and should start 
reporting them to the syslog.

if you encounter any problems during these steps then please let us know 
- this code is quite fresh so expect some rough edges.


      reply	other threads:[~2008-02-14  6:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14  1:12 Kevin Winchester
2008-02-14  6:07 ` Ingo Molnar [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: Latency issues with x86.git' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).