public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li Weichen" <iaadoa@gmail.com>
To: linux-omap-open-source@linux.omap.com
Subject: OSK RAM damage?
Date: Fri, 21 Apr 2006 10:52:55 +0800	[thread overview]
Message-ID: <4448491c.45fa3ac3.3d8f.ffff86aa@mx.gmail.com> (raw)

Hi guys,

I guess the RAM my OSK is damaged!

I have tried mtest command in U-boot for four or five times, after that the
OSK died off, even I pressed reset key it has no reply.  Only the D9 diode
was turned on.

Before this, I was trying the kernel 2.6.16.9 but always met "Unable to
handle kernel paging request at virtual address" error.  And when I used the
former kernels (2.6.14-omap1 is most recently), it had sometimes came up
with segmentation errors.

And further more, when I use the mtest command in U-boot, it shows the
message that "writing..." but without any other information or response.
Does it means that the ram is damaged?

p.s. My OSK is rev.D, and the ram is from ELPIDA.

Regards,


Li Weichen

             reply	other threads:[~2006-04-21  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21  2:52 Li Weichen [this message]
2006-04-24  7:02 ` OSK RAM damage? Hiroki Kaminaga

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=4448491c.45fa3ac3.3d8f.ffff86aa@mx.gmail.com \
    --to=iaadoa@gmail.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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