linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: Bad Page dump (help)
Date: Thu, 31 Jul 2014 18:04:14 -0500	[thread overview]
Message-ID: <20140731230414.GA8920@saruman.home> (raw)
In-Reply-To: <20140731153027.GG19512@saruman.home>

Hi,

On Thu, Jul 31, 2014 at 10:30:27AM -0500, Felipe Balbi wrote:

<snip>

> > I'm suspecting that you either have badly a routed data bus connection
> > on bits 23:16, or you have a bad RAM chip which corrupts those bits.
> > 
> > It may be worth trying a simple assembly-level RAM test which pokes
> > all locations with alternating 0xffffffff, 0x00000000 and verifies
> > them.  By that I mean odd word addresses set to one value, even set
> > to the other, verify, reverse them, try again.
> > 
> > Alternatively, if there's a proper ARM memory checker around, I think
> > it would be well worth running it on this board to check the integrity
> > of the hardware.
> 
> I'll try u-boot's memtester and see what results it yields.

alright, stock u-boot's memtest didn't help much, so I modified it a bit
and started seen issues when I was testing only the first 4MiB of RAM.
Here's one small snippet of the output:

RET    ADDR            WR          RD

FAIL @ 80000010 exp fffffffd got ffeafffd
FAIL @ 80001c30 exp fffffe3b got fffbfe3b
FAIL @ 80000630 exp ffffff9b got fffbff9b
FAIL @ 80000430 exp ffffffbb got ff5bffbb

So what I just did is that I changed u-boot so it was test 768MiB and
I'll leave this running for the next 4 days or so, then I'll report
here. In any case, thanks for pointing me in the right direction.

cheers

-- 
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140731/d598b84e/attachment.sig>

  reply	other threads:[~2014-07-31 23:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 19:07 Bad Page dump (help) Felipe Balbi
2014-07-29 19:55 ` Russell King - ARM Linux
2014-07-29 20:17   ` Felipe Balbi
2014-07-31 14:53     ` Russell King - ARM Linux
2014-07-31 15:30       ` Felipe Balbi
2014-07-31 23:04         ` Felipe Balbi [this message]
2014-07-31  6:24 ` Gilles Chanteperdrix
2014-07-31 13:43   ` Felipe Balbi
2014-07-31 14:23     ` Felipe Balbi
2014-07-31 14:00   ` Russell King - ARM Linux
2014-07-31 17:42     ` Gilles Chanteperdrix

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=20140731230414.GA8920@saruman.home \
    --to=balbi@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).