mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Arno Euteneuer <Arno.Euteneuer@toptica.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] sporadic crashes of shell commands
Date: Fri, 17 Jan 2014 13:04:03 +0000	[thread overview]
Message-ID: <49BD654B8E52F64BBC06DF3F86638DFAF5A05C@MSE1MUC.toptica.com> (raw)
In-Reply-To: <52D909B4.1050206@corscience.de>

Hi Tim,

> I discovered similar problems on an AM37xx and OMAP35xx with Linux 3.4
> and 3.3.
> 
> > Any ideas of what could be wrong will be highly appreciated.
> Did you try to activate all the Kernel Arm-Errata?
> At least for OMAP3503D we figured out that it suffers from more than
> what the Kernel-Doc says: https://lkml.org/lkml/2013/2/18/349
> 
> With all erratas enabled, the AM37xx was (in my opinion) more stable.
>
That's very interesting.
 
> > We also ruled out the kernel because running our kernel (build with
> > OSELAS-Toolchain) in an ELDK rootfs showed no problems.
> [..]
> >  I would love to understand what is causing these problems and would
> > highly appreciate any suggestion.
> Yes, but you could try the errata and when they work, they may give you
> a good hint what the real problem (maybe in the toolchain) is.
> 
Yes, that's certainly worth a try. 
I didn't play around with the errata, yet, as I'm not deep enough in that topic and I hope these settings had been optimized by others.

Thanks for that hint!!

Best regards
Arno

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-01-17 13:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 10:16 Arno Euteneuer
2014-01-17 10:45 ` Tim Niemeyer
2014-01-17 13:04   ` Arno Euteneuer [this message]
2014-01-20  7:49     ` Arno Euteneuer
2014-01-17 11:15 ` Jürgen Beisert
2014-01-17 12:50   ` Arno Euteneuer
2014-01-17 13:20     ` Jürgen Beisert

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=49BD654B8E52F64BBC06DF3F86638DFAF5A05C@MSE1MUC.toptica.com \
    --to=arno.euteneuer@toptica.com \
    --cc=ptxdist@pengutronix.de \
    /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