From: Chuck Ebbert <76306.1226@compuserve.com>
To: David Chinner <dgc@sgi.com>
Cc: "xfs-masters@oss.sgi.com" <xfs-masters@oss.sgi.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jesper Juhl <jesper.juhl@gmail.com>
Subject: Re: 2.6.19-rc6 : Spontaneous reboots, stack overflows - seems to implicate xfs
Date: Sun, 26 Nov 2006 01:14:22 -0500 [thread overview]
Message-ID: <200611260118_MC3-1-D2E7-B327@compuserve.com> (raw)
In-Reply-To: <20061124005528.GF11034@melbourne.sgi.com>
On Fri, 24 Nov 2006 11:55:28 +1100, David Chinner wrote:
> Also, that means that while XFS is apparently only using <1500 bytes
> of stack through this path according to the static stack checker
> tool, there's more than 2k of extra stack usage that the tool is not
> telling me about. i.e. XFS and whatever is above/below it should
> have a full 4k to work with. I'd really like to know where that
> extra stack space is being used....
You could try applying the (untested) patch below and booting with
the parameter "kstack=2048", then regenerate the problem stack
traces. This should give you a complete raw stack dump in addition
to the call trace for each overflow.
(Output could get very large, so maybe adding a counter and stopping
after ~100 events might also be a good idea.)
--- 2.6.19-rc6-32smp.orig/arch/i386/kernel/irq.c
+++ 2.6.19-rc6-32smp/arch/i386/kernel/irq.c
@@ -80,7 +80,7 @@ fastcall unsigned int do_IRQ(struct pt_r
if (unlikely(esp < (sizeof(struct thread_info) + STACK_WARN))) {
printk("do_IRQ: stack overflow: %ld\n",
esp - sizeof(struct thread_info));
- dump_stack();
+ show_stack();
}
}
#endif
--
Chuck
"Even supernovas have their duller moments."
reply other threads:[~2006-11-26 6:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200611260118_MC3-1-D2E7-B327@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=dgc@sgi.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.com \
/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
all inboxes | Powered by JetHome®