Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, nostop-machine, update stack tracer

From: Steven Rostedt
Date: Thu Jan 05 2012 - 06:46:52 EST


On Thu, 2012-01-05 at 10:19 +0100, Ingo Molnar wrote:
> * Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> > I actually haven't looked at the NMI branch yet. I'm still
> > trying to figure out why the ftrace one would lockup. I'll try
> > another box to see if that one also locks up on tip/master
> > with your config.
>
> Any update on this?

No, for some reason my other box doesn't want to boot your config (no
root found). But I noticed that my first box fails on tip/master with
just my min-config. I ran the bisect and hit this as the bad commit:


commit 41e95d95208c62d4b0fbcee5f16d93e23ca32984
Author: Ingo Molnar <mingo@xxxxxxx>
Date: Thu Sep 17 23:12:20 2009 +0200

<not-for-merge> Disable DEVTMPFS_MOUNT for now

Causing bootup problems - /dev/zero and /dev/null not being there, etc.

NOT-Signed-off-by: Ingo Molnar <mingo@xxxxxxx>

diff --git a/drivers/base/Kconfig b/drivers/base/Kconfig
index ee37727..c52aaad 100644
--- a/drivers/base/Kconfig
+++ b/drivers/base/Kconfig
@@ -28,6 +28,7 @@ config DEVTMPFS
config DEVTMPFS_MOUNT
bool "Automount devtmpfs at /dev"
depends on DEVTMPFS
+ depends on 0
help
This will mount devtmpfs at /dev if the kernel mounts the root
filesystem. It will not affect initramfs based mounting.


When I reverted this, my machine booted. I'm now trying that machine
again with your allyesconfig.

Is there other strange things in tip/master that I should be aware
about?

Again, do you see these errors when just booting my branch directly?
(not merging the branch into another branch).


>
> 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.

Thanks,

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/