From: Greg Watson <gwatson@lanl.gov>
To: linuxppc-dev@lists.linuxppc.org
Subject: Boot code stack size
Date: Wed, 28 Jan 2004 16:59:29 -0700 [thread overview]
Message-ID: <p06020429bc3df88e63e3@[10.0.1.2]> (raw)
I'm working on the PPC LinuxBIOS project and have recently managed to
boot the Sandpoint (Altimus 7410 PMC) using the latest
linuxppc_2_4_devel kernel (2.4.24-pre2).
However while getting Linux to run on this machine, I hit a problem
with this and earlier kernels running out of stack while
uncompressing the kernel image. The symptom I see is that inflate
returns -3 (FFFFFFFD). To get around the problem, I have to modify
arch/ppc/boot/common/relocate.S and increase the stack size from 8K
(4096*2) to 28K (4096*7). The kernel image is 792890 bytes compressed
and 1734312 bytes uncompressed. The Sandpoint boots reliably with the
increased stack size.
I'm wondering a) if anyone has seen this problem while booting other
PPC based systems, and b) if it would be worth adding a configuration
option that allows this early stack size to be specified, rather than
hard-coding it in relocate.S.
Regards,
Greg
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2004-01-28 23:59 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='p06020429bc3df88e63e3@[10.0.1.2]' \
--to=gwatson@lanl.gov \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).