From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@lists•ozlabs.org
Cc: linuxppc-dev <linuxppc-dev@ozlabs•org>, hank peng <pengxihan@gmail•com>
Subject: Re: Is it normal when kernel printed "xxx used greatest stack depth"
Date: Thu, 28 Jan 2010 21:35:47 +0100 [thread overview]
Message-ID: <201001282135.47372.arnd@arndb.de> (raw)
In-Reply-To: <389deec71001280753n2df39d98m4b8c60f971a29bc7@mail.gmail.com>
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
prev parent reply other threads:[~2010-01-28 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201001282135.47372.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=pengxihan@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox