From: Embedded Engineer <embed786@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Unstable Kernel behavior on an ARM based board
Date: Mon, 4 Mar 2019 10:14:50 +0500 [thread overview]
Message-ID: <CA+_ZnZTrGCzPLKWZdxBzV1Z9b+c-Sp27DeUeV2XFW0+ZNZipGw@mail.gmail.com> (raw)
In-Reply-To: <453072a9-52e2-7591-750f-624ca27e0bbf@gmx.net>
On Sat, Mar 2, 2019 at 8:07 PM Clemens Koller <clemens.ml@gmx.net> wrote:
> The behaviour looks familiar to me if RAM timing is off. The memory initialization might not be suitable for your PCB design.
> You can try to exercise some in-depth memory tests from within u-boot up to the temperature extremes of your hardware, before you switch over to linux. Checkout "mtest".
Thanks Clemens, we did consider enabling mtest in our u-boot and using
it but dropped the plan because of the description given on
https://github.com/endlessm/u-boot/blob/master/doc/README.memory-test,
specifically the following statement:
"This is probably the best known memory test utility in U-Boot.
Unfortunately, it is also the most problematic, and the most useless
one."
Do you suggest board redesign is only option left?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-04 5:15 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 10:44 Unstable Kernel behavior on an ARM based board Embedded Engineer
2019-03-02 11:00 ` Russell King - ARM Linux admin
2019-03-02 11:01 ` Willy Tarreau
2019-03-02 11:22 ` Embedded Engineer
2019-03-02 11:25 ` Willy Tarreau
2019-03-02 11:46 ` Russell King - ARM Linux admin
2019-03-04 13:57 ` Thierry Reding
2019-03-02 11:36 ` Russell King - ARM Linux admin
2019-03-02 11:52 ` Embedded Engineer
2019-03-02 11:57 ` Russell King - ARM Linux admin
2019-03-02 12:20 ` Embedded Engineer
2019-03-02 12:39 ` Russell King - ARM Linux admin
2019-03-02 13:10 ` Embedded Engineer
2019-03-02 15:07 ` Clemens Koller
2019-03-04 5:14 ` Embedded Engineer [this message]
2019-03-04 10:26 ` Vladimir Murzin
2019-03-04 12:25 ` Embedded Engineer
2019-03-04 14:25 ` Thierry Reding
2019-03-04 15:51 ` Embedded Engineer
2019-03-04 15:51 ` Embedded Engineer
2019-03-05 10:01 ` Embedded Engineer
2019-03-05 10:01 ` Embedded Engineer
2019-03-05 10:07 ` Russell King - ARM Linux admin
2019-03-05 10:07 ` Russell King - ARM Linux admin
2019-03-05 10:29 ` Embedded Engineer
2019-03-05 10:29 ` Embedded Engineer
2019-03-05 11:20 ` Thierry Reding
2019-03-05 11:22 ` Russell King - ARM Linux admin
2019-03-05 11:22 ` Russell King - ARM Linux admin
2019-03-05 11:57 ` Thierry Reding
2019-03-05 13:16 ` Embedded Engineer
2019-03-05 13:16 ` Embedded Engineer
2019-03-05 13:23 ` Russell King - ARM Linux admin
2019-03-05 13:23 ` Russell King - ARM Linux admin
2019-03-05 13:32 ` Embedded Engineer
2019-03-05 13:32 ` Embedded Engineer
2019-03-05 14:23 ` Russell King - ARM Linux admin
2019-03-05 14:23 ` Russell King - ARM Linux admin
2019-03-05 14:57 ` Embedded Engineer
2019-03-05 14:57 ` Embedded Engineer
2019-03-05 14:58 ` Russell King - ARM Linux admin
2019-03-05 14:58 ` Russell King - ARM Linux admin
2019-03-05 15:11 ` Embedded Engineer
2019-03-05 15:11 ` Embedded Engineer
2019-03-05 15:31 ` Russell King - ARM Linux admin
2019-03-05 15:31 ` Russell King - ARM Linux admin
2019-03-05 15:44 ` Embedded Engineer
2019-03-05 15:44 ` Embedded Engineer
2019-03-15 8:55 ` Marcel Ziswiler
2019-03-15 8:55 ` Marcel Ziswiler
2019-03-05 16:00 ` Clemens Koller
2019-03-05 16:21 ` Embedded Engineer
2019-03-09 7:50 ` Embedded Engineer
2019-03-09 7:50 ` Embedded Engineer
2019-03-05 10:32 ` Thierry Reding
2019-03-05 11:05 ` Embedded Engineer
2019-03-05 11:05 ` Embedded Engineer
2019-03-05 11:36 ` Thierry Reding
2019-03-04 14:00 ` Andrew Lunn
2019-03-04 14:27 ` Thierry Reding
2019-03-04 15:27 ` Embedded Engineer
2019-03-04 15:57 ` Andrew Lunn
2019-03-04 16:03 ` Embedded Engineer
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=CA+_ZnZTrGCzPLKWZdxBzV1Z9b+c-Sp27DeUeV2XFW0+ZNZipGw@mail.gmail.com \
--to=embed786@gmail.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 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.