From: Roland Dreier <roland@topspin.com>
To: Eli Cohen <mlxk@mellanox.co.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sysrq shows impossible call stack
Date: 20 Apr 2004 09:26:17 -0700 [thread overview]
Message-ID: <52ekqizkd2.fsf@topspin.com> (raw)
In-Reply-To: <408545AA.6030807@mellanox.co.il>
Eli> Hi, I am exsperiencing a hang, probably caused by a deadlock,
Eli> so I can do sysrq commands. However I can see that in some
Eli> cases the exspected call stack has some functions in between
Eli> as if two call stack are interleaved.
Hi Eli,
I think what you are seeing is old values left on the stack. If a
function allocates space for local variables but bumping the stack
pointer, but then never actually uses those variables, then old values
including old return addresses may be left in the stack.
- Roland
next prev parent reply other threads:[~2004-04-20 16:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 15:45 sysrq shows impossible call stack Eli Cohen
2004-04-20 16:26 ` Roland Dreier [this message]
2004-04-20 17:36 ` Eli Cohen
2004-04-20 17:51 ` stack dumps, CONFIG_FRAME_POINTER and i386 (was Re: sysrq shows impossible call stack) Roland Dreier
2004-04-20 20:26 ` Adam Litke
2004-04-21 0:12 ` Roland Dreier
2004-04-21 1:39 ` Andrew Morton
2004-04-21 1:41 ` Andrew Morton
2004-04-21 23:28 ` Adam Litke
2004-04-21 23:50 ` Andrew Morton
2004-04-22 18:25 ` Adam Litke
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=52ekqizkd2.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlxk@mellanox.co.il \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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