lkml.org 
[lkml]   [2007]   [Dec]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [2.6.23(?)=<] X used greatest stack depth: N bytes left
    On 12/29/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
    > On Sat, 29 Dec 2007 01:58:44 +0100 Oliver Pinter (Pintér Olivér) wrote:
    >
    > > On 12/29/07, Randy Dunlap <randy.dunlap@oracle.com> 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
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-12-29 03:39    [W:0.031 / U:96.860 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site