All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: imx6 silent memory corruption
Date: Thu, 22 Jan 2015 23:25:10 +0200	[thread overview]
Message-ID: <54C16AB6.20605@mail.bg> (raw)

Hi folks,

I observe a behavior of my system, which I think is a silent memory
corruption. My setup is imx6d, 3.10.17-1.0.0ga, daisy. Here's a simple
script that usually should not fail:


set -e

for i in `seq 1 100`; do
     echo "Test $i"
     sha256sum -c test.dat.sha256
done


test.dat contains 64MB random data, test.dat.sha256 contains the SHA256
file hash.

The files are copied in /tmp and test is run there, to avoid unwanted
interactions with most of the filesystem drivers and storage devices.
What actually happens is that sooner or later the hash verification
fails, which should not happen (and doesn't happen on my x64
workstation). During the verification failure there are no errors in
the system log.

Performed also a similar test where I compared in a loop the content of
2 copies of the same file, and again after some iterations the
comparison fails, neither with system log errors, nor oopses.

I will appreciate if you can share ideas what could be wrong with this
setup, and also I'll be happy to hear from you suggestions for similar
simple tests for system reliability.

Regards,
Nikolay


             reply	other threads:[~2015-01-22 21:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 21:25 Nikolay Dimitrov [this message]
2015-01-22 22:25 ` imx6 silent memory corruption Fabio Estevam
2015-01-23 21:11   ` Nikolay Dimitrov
2015-01-26 14:40     ` Doug Schwanke
2015-01-27  8:40       ` Nikolay Dimitrov
2015-01-27 16:27         ` Nikolay Dimitrov
2015-01-27 17:00           ` Otavio Salvador
2015-01-27 17:40             ` Gonzalez, Alex
2015-01-27 20:23               ` Nikolay Dimitrov
2015-01-27 20:51                 ` Eric Bénard
2015-01-27 22:35                   ` Nikolay Dimitrov
2015-01-27 22:59                     ` Eric Bénard
2015-01-28 16:18                       ` Nikolay Dimitrov
2015-01-28 16:40                         ` Fabio Estevam
2015-02-14 12:12                       ` Nikolay Dimitrov

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=54C16AB6.20605@mail.bg \
    --to=picmaster@mail.bg \
    --cc=meta-freescale@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.