Subject: Help Understanding what causes kernel stack overflow.
From: GrandMasterLee <masterlee@digitalroadkill.net>
To: linux-kernel@vger.kernel.org
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1039827096.31946.23.camel@UberGeek>
Mime-Version: 1.0
Date: 13 Dec 2002 18:51:36 -0600
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1499
Lines: 34

Kernel: 2.4.19-aa1
FS are all XFS. Kernel has no modules, except Qlogic drivers(6.01-fo)

I've been dealing with some pretty regular, albeit severe stack overflow
issues which crashes one of my two DB servers from time to time. We
currently are on a schedule to reboot them every week to prevent the
systems from hanging/crashing/etc. 

We recently were able to make some correlation to backup times and the
potential stack overflow detection messages. I've got a traces from our
kernel log and messages files. I was curious if there were currently any
tools to examine the stack call traces in detail. 

I tried using ksymoops, but it really didn't give me any more than I
already had in messages. Any advice on the *best* way to proceed
debugging what is causing stack overflows given I have the call traces?

Currently, I've dumped all the objects from the running kernel(objdump
-Dr vmlinux) and will search for the "sub" lines which correspond to
%esp. I'll then take the functions which are listed in my call trace,
and add up the total each function uses to see if that is the right
path, then to try an reproduce it, given the call traces I have. 


Any help on doing this would be wonderful. 


-- 
GrandMasterLee <masterlee@digitalroadkill.net>
-
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/