From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from gateway.tuioptics.com ([213.183.22.85]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1W59cQ-0006ym-FU for ptxdist@pengutronix.de; Mon, 20 Jan 2014 08:50:03 +0100 From: Arno Euteneuer Date: Mon, 20 Jan 2014 07:49:56 +0000 Message-ID: <49BD654B8E52F64BBC06DF3F86638DFAF5A1BC@MSE1MUC.toptica.com> References: <49BD654B8E52F64BBC06DF3F86638DFAF59FF7@MSE1MUC.toptica.com> <52D909B4.1050206@corscience.de> <49BD654B8E52F64BBC06DF3F86638DFAF5A05C@MSE1MUC.toptica.com> In-Reply-To: <49BD654B8E52F64BBC06DF3F86638DFAF5A05C@MSE1MUC.toptica.com> Content-Language: de-DE MIME-Version: 1.0 Subject: Re: [ptxdist] sporadic crashes of shell commands Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: "ptxdist@pengutronix.de" Good morning, As Tim suggested I enabled all available errata in my kernel configuration = and rebuild kernel and rootfs with my old OSELAS toolchain. I didn't get a = single illegal instruction or segfault during the weekend from our test scr= ipts, even though the CPU was running with 100% load all the time. Thank you very much, Tim! This seems to be the trick. I only have two questions now: 1. Why did the other toolchain help? What was its influence? Do toolchains = have built-in erratas for certain processors? 2. Are there disadvantages of certain errata? Why are they selectable in th= e kernel config and not integrated into the respective architecture's sourc= es by default? Best regards Arno > -----Urspr=FCngliche Nachricht----- > Von: ptxdist-bounces@pengutronix.de [mailto:ptxdist- > bounces@pengutronix.de] Im Auftrag von Arno Euteneuer > Gesendet: Freitag, 17. Januar 2014 14:04 > An: ptxdist@pengutronix.de > Betreff: Re: [ptxdist] sporadic crashes of shell commands > = > 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 -- = ptxdist mailing list ptxdist@pengutronix.de