From: Steven Rostedt <rostedt@goodmis.org>
To: John Rigg <lk@sound-man.co.uk>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.14-rc3-rt10 crashes on boot
Date: Fri, 7 Oct 2005 11:48:42 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0510071146370.7222@localhost.localdomain> (raw)
In-Reply-To: <E1ENtsV-00018l-5z@localhost.localdomain>
On Fri, 7 Oct 2005, John Rigg wrote:
> On Friday 7 October 2005 Ingo Molnar wrote:
> >i got overflows in initramfs's gunzip with certain debug options. I have
> >improved the stack footprint of the worst offenders in -rt11 (see the
> >standalone patch below) - John, does it boot any better?
>
> Ah. I'm using initrd. With CONFIG_LATENCY_TRACE=y my initrd.img is
> large, > 3.6MB. Maybe it's time to try initramfs.
>
> BTW I'm having trouble enabling DEBUG_STACKOVERFLOW. I can see
> it in arch/i386/Kconfig.debug (and not in arch/x86_64/Kconfig.debug),
> but it doesn't appear in menuconfig no matter what other kernel hacking
> options I enable. If I add it manually to .config it just gets removed
> by `make oldconfig'. Is this an x86_64 issue?
>
> For now I'll assume that there is a stack overflow and try initramfs.
>
Here John,
Add this patch and it will add the option for you in x86_64 (I forgot that
you were using that). I even set it to be default on. I didn't add a test
in do_IRQ, but I believe that the tests in latency.c should be good
enough.
-- Steve
Index: linux-rt-quilt/arch/x86_64/Kconfig.debug
===================================================================
--- linux-rt-quilt.orig/arch/x86_64/Kconfig.debug 2005-08-28 19:41:01.000000000 -0400
+++ linux-rt-quilt/arch/x86_64/Kconfig.debug 2005-10-07 11:43:45.000000000 -0400
@@ -33,6 +33,14 @@
options. See Documentation/x86_64/boot-options.txt for more
details.
+config DEBUG_STACKOVERFLOW
+ bool "Check for stack overflows"
+ depends on DEBUG_KERNEL
+ default y
+ help
+ This option will cause messages to be printed if free stack space
+ drops below a certain limit.
+
config KPROBES
bool "Kprobes"
depends on DEBUG_KERNEL
next prev parent reply other threads:[~2005-10-07 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 15:11 John Rigg
2005-10-07 15:48 ` Steven Rostedt [this message]
[not found] <E1EOe3U-00018A-Fy@localhost.localdomain>
2005-10-11 11:17 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-10-09 16:30 John Rigg
2005-10-09 16:28 John Rigg
[not found] <E1ENxei-0001C9-F7@localhost.localdomain>
2005-10-07 19:42 ` Steven Rostedt
2005-10-11 10:55 ` Ingo Molnar
2005-10-07 19:16 John Rigg
2005-10-07 0:37 John Rigg
2005-10-07 6:36 ` Steven Rostedt
2005-10-07 11:43 ` Ingo Molnar
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=Pine.LNX.4.58.0510071146370.7222@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@sound-man.co.uk \
--cc=mingo@elte.hu \
/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®