From: Randy Dunlap <rdunlap@xenotime.net>
To: Edward Goggin <egoggin@emc.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: looking for explanation of spontaneous reset/reboot on Opteron
Date: Thu, 12 Oct 2006 14:06:44 -0700 [thread overview]
Message-ID: <20061012140644.732227f7.rdunlap@xenotime.net> (raw)
In-Reply-To: <6CCEAEDF4D06984A83F427424F47D6E4013D1446@CORPUSMX40A.corp.emc.com>
On Thu, 12 Oct 2006 13:43:15 -0400 Edward Goggin wrote:
> I'm looking for information about potential causes for a
> spontaneous reboot of a dual core Opteron running RHEL 4
> linux (2.6.9 derivative). I'm thinking the cause is
> due to the box taking a triple fault and resetting the
> BIOS.
>
> I'm also thinking that the triple fault is caused by a
> kernel stack overflow into an unmapped virtual page
> frame. Is this a reasonable explanation? Are there
> others?
>
> What are reasonable debugging strategies for handling
> this? Following the kernel stack overflow hunch, I'm
> going to try increasing the Opteron stack size from
> 8K to 16K. Can this be done by simply changing
> THREAD_ORDER in include/asm-x86_64/page.h from 1 to 2?
>
> Also, is there any kernel stack overflow detection
> debugging code anywhere for x86_64 as there is for
> i386?
[Please start a new thread instead of replying to a diff.
one and changing the subject.]
arch/x86_64/Kconfig.debug has these Kernel hacking options:
[but I'm not talking about 2.6.9; maybe you should/could try
a newer kernel]
config DEBUG_STACKOVERFLOW
bool "Check for stack overflows"
depends on DEBUG_KERNEL
help
This option will cause messages to be printed if free stack space
drops below a certain limit.
config DEBUG_STACK_USAGE
bool "Stack utilization instrumentation"
depends on DEBUG_KERNEL
help
Enables the display of the minimum amount of free stack which each
task has ever had available in the sysrq-T and sysrq-P debug output.
This option will slow down process creation somewhat.
---
~Randy
prev parent reply other threads:[~2006-10-12 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 16:33 [PATCH] Remove lilo-loads-only-five-sectors-of-zImage-fixup from setup.S Alexander van Heukelum
2006-10-11 18:38 ` H. Peter Anvin
2006-10-11 19:43 ` Alexander van Heukelum
2006-10-11 19:43 ` H. Peter Anvin
2006-10-12 16:57 ` John Coffman
2006-10-12 17:04 ` H. Peter Anvin
2006-10-12 18:15 ` Alexander van Heukelum
2006-10-12 17:43 ` looking for explanation of spontaneous reset/reboot on Opteron Edward Goggin
2006-10-12 21:06 ` Randy Dunlap [this message]
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=20061012140644.732227f7.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=egoggin@emc.com \
--cc=linux-kernel@vger.kernel.org \
/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®