From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753743AbYITOLw (ORCPT ); Sat, 20 Sep 2008 10:11:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751236AbYITOLo (ORCPT ); Sat, 20 Sep 2008 10:11:44 -0400 Received: from pih-relay04.plus.net ([212.159.14.17]:36707 "EHLO pih-relay04.plus.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751128AbYITOLn (ORCPT ); Sat, 20 Sep 2008 10:11:43 -0400 Message-ID: <48D50498.5050608@yahoo.com> Date: Sat, 20 Sep 2008 15:11:36 +0100 From: Sitsofe Wheeler User-Agent: Thunderbird 2.0.0.16 (Macintosh/20080707) MIME-Version: 1.0 Newsgroups: gmane.linux.kernel To: Steven Rostedt CC: Peter Zijlstra , Ingo Molnar , Arjan van de Ven , 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?) References: <48D4CC1B.7030708@yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: fa56d807dbbbada94c8c6811ceb8b074 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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/