* Is it normal when kernel printed "xxx used greatest stack depth"
@ 2010-01-28 15:53 hank peng
2010-01-28 20:35 ` Arnd Bergmann
0 siblings, 1 reply; 2+ messages in thread
From: hank peng @ 2010-01-28 15:53 UTC (permalink / raw)
To: linuxppc-dev
On my MPC8548 based board, sometimes kernel printed out the following
messages, I wonder if it indicates the system is not normal?
pdflush used greatest stack depth: 4048 bytes left
pdflush used greatest stack depth: 4028 bytes left
pdflush used greatest stack depth: 3964 bytes left
pdflush used greatest stack depth: 3916 bytes left
--
The simplest is not all best but the best is surely the simplest!
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Is it normal when kernel printed "xxx used greatest stack depth"
2010-01-28 15:53 Is it normal when kernel printed "xxx used greatest stack depth" hank peng
@ 2010-01-28 20:35 ` Arnd Bergmann
0 siblings, 0 replies; 2+ messages in thread
From: Arnd Bergmann @ 2010-01-28 20:35 UTC (permalink / raw)
To: linuxppc-dev; +Cc: linuxppc-dev, hank peng
On Thursday 28 January 2010, hank peng wrote:
> On my MPC8548 based board, sometimes kernel printed out the following
> messages, I wonder if it indicates the system is not normal?
>
> pdflush used greatest stack depth: 4048 bytes left
> pdflush used greatest stack depth: 4028 bytes left
> pdflush used greatest stack depth: 3964 bytes left
> pdflush used greatest stack depth: 3916 bytes left
It's a debug option that you have enabled in the kernel configuration.
3916 bytes left is not unusual, there is nothing to worry here,
but on production systems, you might want to disable
CONFIG_DEBUG_STACK_USAGE.
Arnd
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-01-28 20:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-28 15:53 Is it normal when kernel printed "xxx used greatest stack depth" hank peng
2010-01-28 20:35 ` Arnd Bergmann
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox