public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Stuart_Hayes@Dell.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI stack overflow
Date: 06 Mar 2004 00:13:06 +0100	[thread overview]
Message-ID: <p731xo651ml.fsf@brahms.suse.de> (raw)
In-Reply-To: <CE41BFEF2481C246A8DE0D2B4DBACF4F128AA1@ausx2kmpc106.aus.amer.dell.com.suse.lists.linux.kernel>

Stuart_Hayes@Dell.com writes:

> Hello...
> 
> I think I am getting a stack overflow when Linux is parsing the ACPI tables (initializing all the devices and running all the _STA methods).  I am using the x86_64 architecture.  I would like to try increasing the kernel stack size, but I'm not sure how to go about doing this.  Could someone tell me how to increase the kernel stack size?  (And, has anyone else seen a problem with stack overflows with ACPI?)

Increasing THREAD_ORDER to 2 in include/asm-x86_64/page.h should do 
the trick in theory (not tested). There is also an old 2.4 exact stack
overflow checking patch at ftp://ftp.x86-64.org/pub/linux/debug/stackcheck-1
that could be probably ported to newer kernels.

I haven't heard of ACPI stack overflows before.

-Andi

  parent reply	other threads:[~2004-03-05 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 21:01 ACPI stack overflow Stuart_Hayes
2004-03-05 21:51 ` Richard B. Johnson
2004-03-05 22:35 ` Chris Wedgwood
     [not found] ` <CE41BFEF2481C246A8DE0D2B4DBACF4F128AA1@ausx2kmpc106.aus.amer.dell.com.suse.lists.linux.kernel>
2004-03-05 23:13   ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-05 22:38 Stuart_Hayes

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=p731xo651ml.fsf@brahms.suse.de \
    --to=ak@suse.de \
    --cc=Stuart_Hayes@Dell.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