Re: [2.6.30-rcX] Some ftrace debug option is consuming memory?
From: Tetsuo Handa
Date: Tue May 26 2009 - 21:47:00 EST
Steven Rostedt wrote:
> > I was running a VM with 1024MB of RAM.
> > I changed it to 512MB of RAM, and now I'm experiencing out of memory error.
> How many virtual CPUs do you have configured?
I assigned 2 virtual CPUs.
But this error occurs even with 1 virtual CPU.
> > 22.214.171.124 can boot with 512MB of RAM.
> > 2.6.30-rc1 and later cannot boot with 512MB of RAM if some debug options are
> > enabled.
> Did 29.4 have tracing enabled and still worked?
Config (with all tracing options enabled) is at http://I-love.SAKURA.ne.jp/tmp/config-126.96.36.199-ok
Full log is at http://I-love.SAKURA.ne.jp/tmp/dmesg-188.8.131.52-ok-512MB.txt
> > < # CONFIG_IRQSOFF_TRACER is not set
> > < # CONFIG_SYSPROF_TRACER is not set
> > < # CONFIG_SCHED_TRACER is not set
> Can you also disable the above three and see if you still see problems?
I disabled the above three.
# diff config-2.6.30-rc7-ng .config
< # Mon May 25 13:28:39 2009
> # Wed May 27 10:11:09 2009
> # CONFIG_IRQSOFF_TRACER is not set
> # CONFIG_SYSPROF_TRACER is not set
> # CONFIG_SCHED_TRACER is not set
But I'm still seeing the problem.
Full log which cannot boot is at http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.30-rc7-ng-512MB.txt
Full log which can boot is at http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.30-rc7-ng-1024MB.txt
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/