From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: Linux PPC Linux PPC <linuxppc-embedded@ozlabs.org>
Subject: HIGHMEM on 440EPx board with 1GB of RAM
Date: Wed, 23 May 2007 11:41:17 +0200 [thread overview]
Message-ID: <200705231141.18614.matthias.fuchs@esd-electronics.com> (raw)
Hi,
I ran into some trouble with a custom 440EPx board that uses 1GB of RAM
(SO-DIMM module). The board and kernel port is very identical to the AMCC
sequoia board.
The kernel (recent version from Denx 2.6 repository) is configured with
HIGHMEM support.
The most obvious problems are crashes when accessing yaffs2 partitions on NAND
flashes. This seems to be no NAND or yaffs filesystem issue.
My problems dissapear when passing the mem= kernel parameter with mem=768M.
In general the system is stable with the full gig of ram and e.g. not using
yaffs. So I do not believe in a hardware issue.
Can anybody give me a hint where I should start to investigate ?
Matthias
reply other threads:[~2007-05-23 9:47 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=200705231141.18614.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=linuxppc-embedded@ozlabs.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).