From: "dong in kang" <dkang@east.isi.edu>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Memory management problem with RAMDISK, any help?
Date: Tue, 18 May 2004 11:51:24 -0400 [thread overview]
Message-ID: <000e01c43cef$f9180dd0$45a97241@Yongkoo> (raw)
In-Reply-To: <40AA2542.5060306@egholm-nielsen.dk>
Hello,
My Linux (v.2.4.22) running on a PowerPC 750 system does not seem to know
the memory bound when ramdisk is installed. The system has 128 M memory and
28 Meg of the memory is used as ramdisk. I setup the memory size as 128M
bytes at the kernel parameter and ppc_md.find_end_of_memory() routine
returns constant 128M.
The kernel dies with " Oops: kernel access of bad area, sig: 11".
The area it accessed is the start of the last 28 Megabytes of the 128 M
memory. It happens when the kernel tries to allocate memory for socket
communication.
How can I know the kernel knows the end of memory correctly?
Could it be other problem?
Thanks,
Dong-In
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-05-18 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 12:29 Interrupt handling triggered by GPIO-input on 405EP? Martin Egholm Nielsen
[not found] ` <008a01c43ce1$9a65fda0$0301a8c0@chuck2>
2004-05-18 15:01 ` Martin Egholm Nielsen
2004-05-18 15:51 ` dong in kang [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='000e01c43cef$f9180dd0$45a97241@Yongkoo' \
--to=dkang@east.isi.edu \
--cc=linuxppc-embedded@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).