in newer kernel I recently see this warnings:
X used greatest stack depth: N bytes left
X E { program name }
N E { x byte }
----------------8<--------------
...
khelper used greatest stack depth: 7496 bytes left
khelper used greatest stack depth: 7184 bytes left
...
khelper used greatest stack depth: 6328 bytes left
stty used greatest stack depth: 6180 bytes left
mount used greatest stack depth: 6156 bytes left
mknod used greatest stack depth: 5932 bytes left
...
wpa_supplicant used greatest stack depth: 5740 bytes left
...
dhclient3 used greatest stack depth: 5500 bytes left
----------------8<--------------
it is the "results" of the CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_STACK_USAGE=y options or it's other problem or feature?
--
Thanks,
Oliver
On Fri, 28 Dec 2007 22:11:25 +0100 Oliver Pinter (Pint?r Oliv?r) wrote:
> in newer kernel I recently see this warnings:
>
> X used greatest stack depth: N bytes left
>
> X E { program name }
> N E { x byte }
>
> ----------------8<--------------
> ...
> khelper used greatest stack depth: 7496 bytes left
> khelper used greatest stack depth: 7184 bytes left
> ...
> khelper used greatest stack depth: 6328 bytes left
> stty used greatest stack depth: 6180 bytes left
> mount used greatest stack depth: 6156 bytes left
> mknod used greatest stack depth: 5932 bytes left
> ...
> wpa_supplicant used greatest stack depth: 5740 bytes left
> ...
> dhclient3 used greatest stack depth: 5500 bytes left
> ----------------8<--------------
>
> it is the "results" of the CONFIG_DEBUG_STACKOVERFLOW=y
> CONFIG_DEBUG_STACK_USAGE=y options or it's other problem or feature?
CONFIG_DEBUG_STACK_USAGE, in kernel/exit.c:
---
~Randy
desserts: http://www.xenotime.net/linux/recipes/
On 12/29/07, Randy Dunlap <[email protected]> wrote:
> On Fri, 28 Dec 2007 22:11:25 +0100 Oliver Pinter (Pint?r Oliv?r) wrote:
>
> > in newer kernel I recently see this warnings:
> >
> > X used greatest stack depth: N bytes left
> >
> > X E { program name }
> > N E { x byte }
> >
> > ----------------8<--------------
> > ...
> > khelper used greatest stack depth: 7496 bytes left
> > khelper used greatest stack depth: 7184 bytes left
> > ...
> > khelper used greatest stack depth: 6328 bytes left
> > stty used greatest stack depth: 6180 bytes left
> > mount used greatest stack depth: 6156 bytes left
> > mknod used greatest stack depth: 5932 bytes left
> > ...
> > wpa_supplicant used greatest stack depth: 5740 bytes left
> > ...
> > dhclient3 used greatest stack depth: 5500 bytes left
> > ----------------8<--------------
> >
> > it is the "results" of the CONFIG_DEBUG_STACKOVERFLOW=y
> > CONFIG_DEBUG_STACK_USAGE=y options or it's other problem or feature?
>
> CONFIG_DEBUG_STACK_USAGE, in kernel/exit.c:
>
> ---
> ~Randy
> desserts: http://www.xenotime.net/linux/recipes/
>
sure, but to 2.6.22 or 2.6.23-rcX (with merged the cfs scheduler)
don't show this warnings, but the CONFIG_DEBUG_STACK_USAGE is enabled.
--
Thanks,
Oliver
On Sat, 29 Dec 2007 01:58:44 +0100 Oliver Pinter (Pint?r Oliv?r) wrote:
> On 12/29/07, Randy Dunlap <[email protected]> wrote:
> > On Fri, 28 Dec 2007 22:11:25 +0100 Oliver Pinter (Pint?r Oliv?r) wrote:
> >
> > > in newer kernel I recently see this warnings:
> > >
> > > X used greatest stack depth: N bytes left
> > >
> > > X E { program name }
> > > N E { x byte }
> > >
> > > ----------------8<--------------
> > > ...
> > > khelper used greatest stack depth: 7496 bytes left
> > > khelper used greatest stack depth: 7184 bytes left
> > > ...
> > > khelper used greatest stack depth: 6328 bytes left
> > > stty used greatest stack depth: 6180 bytes left
> > > mount used greatest stack depth: 6156 bytes left
> > > mknod used greatest stack depth: 5932 bytes left
> > > ...
> > > wpa_supplicant used greatest stack depth: 5740 bytes left
> > > ...
> > > dhclient3 used greatest stack depth: 5500 bytes left
> > > ----------------8<--------------
> > >
> > > it is the "results" of the CONFIG_DEBUG_STACKOVERFLOW=y
> > > CONFIG_DEBUG_STACK_USAGE=y options or it's other problem or feature?
> >
> > CONFIG_DEBUG_STACK_USAGE, in kernel/exit.c:
> >
> > ---
>
> sure, but to 2.6.22 or 2.6.23-rcX (with merged the cfs scheduler)
> don't show this warnings, but the CONFIG_DEBUG_STACK_USAGE is enabled.
Sorry, I couldn't tell that you were asking more than that.
In 2.6.22, CONFIG_DEBUG_STACK_USAGE only causes output during
sysrq-W (show blocked state).
In 2.6.24-rc, CONFIG_DEBUG_STACK_USAGE also causes output during
process exit, which is what you are seeing.
Does that help?
---
~Randy
desserts: http://www.xenotime.net/linux/recipes/
On Sat, 29 Dec 2007 01:58:44 +0100, "=?ISO-8859-1?Q?Oliver_Pinter_(Pint=E9r_Oliv=E9r)?=" said:
> sure, but to 2.6.22 or 2.6.23-rcX (with merged the cfs scheduler)
> don't show this warnings, but the CONFIG_DEBUG_STACK_USAGE is enabled.
>
And I look in your dmesg-2.6.24-rc6-wifi0, and I see in the last 15 lines or so:
Write protecting the kernel text: 3528k
Write protecting the kernel read-only data: 890k
khelper used greatest stack depth: 6328 bytes left
stty used greatest stack depth: 6180 bytes left
mount used greatest stack depth: 6156 bytes left
mknod used greatest stack depth: 5932 bytes left
Adding 2048276k swap on /dev/sda2. Priority:-1 extents:1 across:2048276k
XFS mounting filesystem sda1
Ending clean XFS mount for filesystem: sda1
XFS mounting filesystem sda4
Ending clean XFS mount for filesystem: sda4
skge eth0: enabling interface
ADDRCONF(NETDEV_UP): eth0: link is not ready
wpa_supplicant used greatest stack depth: 5740 bytes left
eth1: no IPv6 routers present
dhclient3 used greatest stack depth: 5500 bytes left
So what message are you saying you don't see? I see a bunch of "used greatest
stack" messages there?
On 12/29/07, Randy Dunlap <[email protected]> wrote:
> On Sat, 29 Dec 2007 01:58:44 +0100 Oliver Pinter (Pint?r Oliv?r) wrote:
>
> > On 12/29/07, Randy Dunlap <[email protected]> wrote:
> > > On Fri, 28 Dec 2007 22:11:25 +0100 Oliver Pinter (Pint?r Oliv?r) wrote:
> > >
> > > > in newer kernel I recently see this warnings:
> > > >
> > > > X used greatest stack depth: N bytes left
> > > >
> > > > X E { program name }
> > > > N E { x byte }
> > > >
> > > > ----------------8<--------------
> > > > ...
> > > > khelper used greatest stack depth: 7496 bytes left
> > > > khelper used greatest stack depth: 7184 bytes left
> > > > ...
> > > > khelper used greatest stack depth: 6328 bytes left
> > > > stty used greatest stack depth: 6180 bytes left
> > > > mount used greatest stack depth: 6156 bytes left
> > > > mknod used greatest stack depth: 5932 bytes left
> > > > ...
> > > > wpa_supplicant used greatest stack depth: 5740 bytes left
> > > > ...
> > > > dhclient3 used greatest stack depth: 5500 bytes left
> > > > ----------------8<--------------
> > > >
> > > > it is the "results" of the CONFIG_DEBUG_STACKOVERFLOW=y
> > > > CONFIG_DEBUG_STACK_USAGE=y options or it's other problem or feature?
> > >
> > > CONFIG_DEBUG_STACK_USAGE, in kernel/exit.c:
> > >
> > > ---
> >
> > sure, but to 2.6.22 or 2.6.23-rcX (with merged the cfs scheduler)
> > don't show this warnings, but the CONFIG_DEBUG_STACK_USAGE is enabled.
>
> Sorry, I couldn't tell that you were asking more than that.
>
> In 2.6.22, CONFIG_DEBUG_STACK_USAGE only causes output during
> sysrq-W (show blocked state).
>
> In 2.6.24-rc, CONFIG_DEBUG_STACK_USAGE also causes output during
> process exit, which is what you are seeing.
>
> Does that help?
yes, thanks, then it's the answer
sorry, for my bad composition/spelling
--
Thanks,
Oliver