[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200905270306.n4R36OD8055752@www262.sakura.ne.jp>
Date: Wed, 27 May 2009 12:06:24 +0900
From: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
To: rostedt@...dmis.org
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: [2.6.30-rcX] Some ftrace debug option is consuming memory?
Hello.
Steven Rostedt wrote:
> I should have noticed this before. I bet if you disable the branch tracers
> you will boot again. The branch tracers makes a table of _all_ branches in
> the kernel. But the change we did between 29 and 30 is that we also make
> it per cpu. On big boxes the cache line hits were so bad that the
> interrupts would take so long that they would live lock the machine.
>
> You configured 2 CPUS so you doubled the size of that table.
>
> To test if this is your issue you can try changing NR_CPUS to 1, or just
> disabled the BRANCH_PROFILERs.
I disabled CONFIG_TRACE_BRANCH_PROFILING and it boots now.
# diff config-2.6.30-rc7-ng .config
4c4
< # Mon May 25 13:28:39 2009
---
> # Wed May 27 11:52:49 2009
1546,1549c1546
< CONFIG_TRACE_BRANCH_PROFILING=y
< CONFIG_PROFILE_ALL_BRANCHES=y
< CONFIG_TRACING_BRANCHES=y
< CONFIG_BRANCH_TRACER=y
---
> # CONFIG_TRACE_BRANCH_PROFILING is not set
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists