From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, lenb@kernel.org,
astarikovskiy@suse.de
Subject: Re: Reading EeePC900 battery info causes stalls (was Re: How how latent should non-preemptive scheduling be?)
Date: Sat, 20 Sep 2008 15:11:36 +0100 [thread overview]
Message-ID: <48D50498.5050608@yahoo.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0809200955360.12824@gandalf.stny.rr.com>
Steven Rostedt wrote:
> The wake up tracing is CONFIG_SCHED_TRACER. If you do not see
> "wakeup" as one of the available tracers in available_tracers, then check
> your dmesg and see if you have CONFIG_FTRACE_STARTUP_TEST enabled. There
> was a known bug that would cause the wakeup tracing to fail the test. When
> a trace fails the startup test, it is disabled.
This is exactly the case (dmesg reports the ftrace wakeup startup test
failed). That's what I get for not reading my dmesg more carefully...
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2008-09-20 14:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.aea4e10hJLpVS/qr4bumSa5e9C0@ifi.uio.no>
[not found] ` <fa.uDmoMIWw4thxpZxpYeSIpVJhAOo@ifi.uio.no>
[not found] ` <fa.RIMmQqN9ybFSKBqOk9Gxi/mOeB4@ifi.uio.no>
[not found] ` <fa.XLGLzP+T4fm9CkeATkS1VL/Yz4Q@ifi.uio.no>
[not found] ` <fa.z8sKLpwDO3qQ15ZJIm152YEty4I@ifi.uio.no>
[not found] ` <fa.KyW7dWWjiSFnFxwdZZLurmVn8qA@ifi.uio.no>
2008-09-20 10:10 ` Reading EeePC900 battery info causes stalls (was Re: How how latent should non-preemptive scheduling be?) Sitsofe Wheeler
2008-09-20 10:25 ` Alexey Starikovskiy
2008-09-20 10:51 ` Sitsofe Wheeler
2008-09-20 10:55 ` Reading EeePC900 battery info causes stalls Sitsofe Wheeler
2008-09-20 11:14 ` Alexey Starikovskiy
2008-09-20 11:23 ` Sitsofe Wheeler
2008-09-20 11:41 ` Sitsofe Wheeler
2008-09-20 12:34 ` Alexey Starikovskiy
2008-09-20 12:50 ` Sitsofe Wheeler
2008-09-20 13:07 ` Alexey Starikovskiy
2008-09-20 13:30 ` Sitsofe Wheeler
2008-09-20 13:59 ` Reading EeePC900 battery info causes stalls (was Re: How how latent should non-preemptive scheduling be?) Steven Rostedt
2008-09-20 14:11 ` Sitsofe Wheeler [this message]
2008-09-20 14:37 ` Steven Rostedt
2008-09-20 17:16 ` Reading EeePC900 battery info causes stalls Sitsofe Wheeler
2008-09-20 21:53 ` Steven Rostedt
2008-09-20 23:18 ` Sitsofe Wheeler
2008-09-21 7:09 ` Ingo Molnar
2008-09-22 6:24 ` Sitsofe Wheeler
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=48D50498.5050608@yahoo.com \
--to=sitsofe@yahoo.com \
--cc=a.p.zijlstra@chello.nl \
--cc=arjan@infradead.org \
--cc=astarikovskiy@suse.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.