lkml.org 
[lkml]   [2012]   [Apr]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [3.4-rc3] Thread overran stack, or stack corrupted
From
Date
On Wed, 2012-04-18 at 00:06 -0400, Dave Jones wrote:

> That just prints out..
>
> # tracer: function
> #
> # entries-in-buffer/entries-written: 0/0 #P:4
> #
> # _-----=> irqs-off
> # / _----=> need-resched
> # | / _---=> hardirq/softirq
> # || / _--=> preempt-depth
> # ||| / delay
> # TASK-PID CPU# |||| TIMESTAMP FUNCTION
> # | | | |||| | |
>
> > I'm also assuming you have CONFIG_STACKTRACE and
> > CONFIG_STACKTRACE_SUPPORT enabled. They should be selected, but configs
> > can always get screwed up.
>
> CONFIG_STACKTRACE_SUPPORT=y
> CONFIG_STACKTRACE=y
>

OK, function tracing is broken on your box. Could you send me your full
config and I'll take a look at it tomorrow. Bed time for me now ;-)

-- Steve




\
 
 \ /
  Last update: 2012-04-18 22:37    [W:0.080 / U:0.016 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site