From: "Vince Asbridge" <vasbridge@sanblaze.com>
To: "'linuxppc-embedded'" <linuxppc-embedded@ozlabs.org>
Subject: Some memory (DDR2 ECC Dual Rank) just doesn't work! Can anyone point me to how to debug this hang?
Date: Wed, 13 Aug 2008 17:21:35 -0400 [thread overview]
Message-ID: <04c601c8fd8a$91022450$4b01a8c0@sanblaze.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
All,
We have an 8548 design, which implements a DDR2 on a SODIMM
We have an issue with dual rank memory (specific part number Viking
VR5DR287218EBSS1), which is a 1G ECC Registered SODIMM part, with two ranks.
Our platform wires CS0 and CS1 to the SODIMM slot.
At uBoot, all is well. Memory is discovered as ECC 533, 1G DDR2 64Bit 4
beat bursts, and mtest can read and write all 1G of the SODIMM.
Here's where things get bad.
If I boot linux (2.6.11 or 2.6.23 kernel), after the kernel image
decompresses, the machine simply HANGS.
The IP address of the board is currently set to 192.168.200.90
The MAC address is 00:11:0d:1d:a2:23
If they don't match your network environment, please change them in U-Boot
and kernel manually.
Hit any key to stop autoboot: 0
## Booting image at fc580000 ...
Image Name: Linux-2.6.11
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1706305 Bytes = 1.6 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image . (HANG)
Other DDR2s (identical except for vendor and # of ranks), work perfectly!
Anyone got a clue what I could look at to try to figure this out?
We've tried enable / disable ECC at uboot
We've tried enable / disable Interleaving at uboot
uboot always works (and can read/write entire DDR), Linux always hangs on
boot!
Please help,
Vince
[-- Attachment #2: Type: text/html, Size: 3082 bytes --]
reply other threads:[~2008-08-13 21:14 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='04c601c8fd8a$91022450$4b01a8c0@sanblaze.com' \
--to=vasbridge@sanblaze.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