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: Re: imx6 silent memory corruption
Date: Tue, 27 Jan 2015 18:27:48 +0200	[thread overview]
Message-ID: <54C7BC84.90104@mail.bg> (raw)
In-Reply-To: <54C74EE4.8070308@mail.bg>

Hi guys,

Just to share my progress so far. My board passed 500+ iterations of
DDR stress testing with the FSL tool (this bloody thing took 2 days to
complete!). Tried the U-Boot integrated memory tests (both quick and
alt), and they didn't show any issues. So I can say that at least the
hardware and DDR settings seems to be OK.

In addition, I tried to disable SMP, L2 & L1 cache support in my kernel
and see what happens, but I can still observe the corruption. I found
that there's an embedded memory tester in the kernel, but only for x86
(CONFIG_MEMTEST), not useful for ARM.

I started to doubt that my 2 cross-build machines (x64 Debian stable)
are maybe producing broken kernels, so did a test cross-build on Ubuntu
14.04, and even did native build on riotboard, but the results are the
same - issue can be still observed.

During boot and operation I sometimes see kernel oopses (I remember
most of them related with execve and filesystem reads), sometimes apps
segfault. Kernel and/or toolchain issues are also possible but I
checked that Daisy has the gcc-4.8+ PR58854 patch, so not very likely,
especially if other Yocto users don't report such issues.

Possible step forward is to try to build original FSL 3.10.17 version
without my local patches, and maybe even build a minimal 3.18+ mainline
kernel to see how it behaves in the same test case. Someone can even
joke that it's time to leave the dusty old Daisy and go forward with
Dizzy and 3.10.53.

Regards,
Nikolay


  reply	other threads:[~2015-01-27 16:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 21:25 imx6 silent memory corruption Nikolay Dimitrov
2015-01-22 22:25 ` 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 [this message]
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=54C7BC84.90104@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.