From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753379Ab2AHLkf (ORCPT ); Sun, 8 Jan 2012 06:40:35 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:59424 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750967Ab2AHLkd (ORCPT ); Sun, 8 Jan 2012 06:40:33 -0500 Date: Sun, 8 Jan 2012 12:38:32 +0100 From: Ingo Molnar To: Steven Rostedt Cc: linux-kernel@vger.kernel.org, Andrew Morton , Frederic Weisbecker Subject: Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer Message-ID: <20120108113832.GD26516@elte.hu> References: <20120102134856.GA32673@elte.hu> <1325635373.12696.4.camel@gandalf.stny.rr.com> <1325635922.12696.8.camel@gandalf.stny.rr.com> <1325653301.12696.20.camel@gandalf.stny.rr.com> <20120104141107.GA24770@elte.hu> <1325696759.12696.24.camel@gandalf.stny.rr.com> <20120105091916.GA22598@elte.hu> <1325764011.12696.38.camel@gandalf.stny.rr.com> <20120107122511.GB28462@elte.hu> <1325975521.7642.22.camel@gandalf.stny.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1325975521.7642.22.camel@gandalf.stny.rr.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt wrote: > On Sat, 2012-01-07 at 13:25 +0100, Ingo Molnar wrote: > > * Steven Rostedt wrote: > > > > > > I'm also seeing build failures with certain configs: > > > > > > > > kernel/trace/trace_stack.c:387:3: error: implicit declaration of function ‘ftrace_set_early_filter’ > > > > [-Werror=implicit-function-declaration] > > > > > > Hmm, your right. It depends on dyn_ftrace to be configured. > > > Strange that my tests didn't catch that as I thought one of my > > > tests compiles with static ftrace. I'll have to look into why > > > my test didn't catch that. I'll send a fix later today. > > > > Hm, i cannot re-test this tree with general randconfig until it > > keeps failing the build. I'll test the NMI bits, to be able to > > exclude those. > > > Ingo, > > I updated the branch by adding the below patch that fixes the bug. You > can apply this and then run your tests again. > > Thanks! > > Please pull the latest tip/perf/core tree, which can be found at: > > git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git > tip/perf/core > > Head SHA1: 96de37b62ca525cd77d2e85aea1472846ee31c4d > > > Steven Rostedt (1): > tracing: Fix compile error when static ftrace is enabled > > ---- > include/linux/ftrace.h | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) Pulled, thanks Steve! I don't get those spontaneous reboots in regular randconfig tests so far - so lets wait until a simpler config triggers it - chances are high that the problem was unrelated to your tree, it just happened to trigger it somehow. Thanks, Ingo