mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Stuart_Hayes@Dell.com
Cc: linux-kernel@vger.kernel.org, andrew.grover@intel.com
Subject: Re: ACPI stack overflow
Date: Fri, 5 Mar 2004 16:51:38 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0403051638001.398@chaos> (raw)
In-Reply-To: <CE41BFEF2481C246A8DE0D2B4DBACF4F128AA1@ausx2kmpc106.aus.amer.dell.com>

On Fri, 5 Mar 2004 Stuart_Hayes@Dell.com wrote:

>
> 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?)
>

Please fix your mailer. In Unix/Linux, we put in a [Enter] ('\n')
every once in awhile, usually every 79 charcters so that a line
of text does not exceed 80 characters. We do not let some indefinite
screen "auto-wrap".

> Thanks!
> Stuart
> stuart_hayes@dell.com

There have been continual changes over the years to reduce the
amount of kernel stack that the kernel uses because kernel stack-
space is "expensive". It needs to be changed in pages.  I think
that if you have a stack-overflow, then you are writing poor
kernel code. In the kernel, do not put arrays on the stack, i.e,
in "local" space. Use kmalloc()/kfree() instead.

Basically, do not increase the stack size. It just masks problems.
It does not make them go away. If you need more stack, you
are doing something wrong.

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-03-05 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 21:01 Stuart_Hayes
2004-03-05 21:51 ` Richard B. Johnson [this message]
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
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=Pine.LNX.4.53.0403051638001.398@chaos \
    --to=root@chaos.analogic.com \
    --cc=Stuart_Hayes@Dell.com \
    --cc=andrew.grover@intel.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®