From: "Absolut Hunter" <absoluthunter@comcast.net>
To: <linuxppc-embedded@ozlabs.org>
Subject: Linux 2.4.25 / MPC8280 / ram config vs Linux instability?
Date: Mon, 11 Jul 2005 06:38:11 -0700 [thread overview]
Message-ID: <20050711134713.D767067C13@ozlabs.org> (raw)
Anybody,
I ran into a peculiar issue, though it could be user error.
I am using U-boot to configure up the SDRAM and SRAM in our system before we
launch Linux. We have 32 Mb of SDRAM and 2 MB of SRAM in the system.
If I leave the SRAM mapped at higher addresses 0x10000000 and SDRAM at
0x00000000, like U-boot defaults to Linux works great. However, my goal is
to map SRAM <8ns speeds> down to the address 0x00000000, to map the vector
table, so I can achieve a very fast interrupt response time.
I hacked U-boot a little bit to remap these addresses, after all the init
code was finished. U-boot relocates itself to higher memory, i.e. the last
2MB's of SDRAM and all is well within U-boot. I ran a 14 hour test on the
memory area to proof it. Now we have 0x02200000 <34M> memory size being
reported to Linux, in the bd->memsize. However, now Linux crashes randomly
all over the place, mostly sig11's task: swapper. I know this is not an
issue with SDRAM stability, and I can't imagine SRAM having problems seeing
as its 8ns capable and we're running at 15ns at the moment (66mhz).
Linux reports BAT mappings as BAT2=32Mb, BAT3=2MB when all 34 Megs are
presented via U-boot.
Does anyone have any idea what would cause this instability? Physically all
memory seems to be great if used by itself. I know very little about how
Linux manages its pages, BATS, TBLs, etc... Are the limits on odd memory
sizes? Or certain configurations that it expects to see?
Thanks in advance.
-Russell McGuire
next reply other threads:[~2005-07-11 13:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 13:38 Absolut Hunter [this message]
2005-07-11 14:01 ` Linux 2.4.25 / MPC8280 / ram config vs Linux instability? Michael Richardson
2005-07-11 14:03 ` Mark Chambers
2005-07-11 14:22 ` Wolfgang Denk
2005-11-02 13:49 ` About 2.6.14 on AMCC Yosemite board KylongMu
2005-11-02 16:46 ` Wolfgang Denk
2005-11-06 15:55 ` Today's 2.6.14 can't finish build with yosemite-defconfig KylongMu
2005-11-11 2:04 ` 11-11-05 2.6.14 on AMCC Yosemite board(boot error) KylongMu
2005-11-11 8:39 ` Wolfgang Denk
2005-11-12 16:47 ` KylongMu
2005-11-12 18:01 ` Problem solved: " KylongMu
2005-11-12 23:32 ` Wolfgang Denk
2005-11-12 23:30 ` Wolfgang Denk
2005-07-11 18:39 ` Linux 2.4.25 / MPC8280 / ram config vs Linux instability? Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2005-07-11 13:59 Steven Blakeslee
2005-07-11 14:02 Absolut Hunter
2005-07-11 14:39 ` Michael Richardson
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=20050711134713.D767067C13@ozlabs.org \
--to=absoluthunter@comcast.net \
--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).