From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] sporadic crashes of shell commands
Date: Fri, 17 Jan 2014 12:15:46 +0100 [thread overview]
Message-ID: <201401171215.46967.jbe@pengutronix.de> (raw)
In-Reply-To: <49BD654B8E52F64BBC06DF3F86638DFAF59FF7@MSE1MUC.toptica.com>
Hi Arno,
On Friday 17 January 2014 11:16:02 Arno Euteneuer wrote:
> [...]
> A while ago we noticed that commands like e.g. lsmod would sometimes crash
> on the target with an Illegal Instruction or segfault, just to work
> correctly again in the next second. Also we sometimes got kicked out of our
> ssh session on the target for no obvious reason. This happened very seldom
> first. However, now after investigating into it, we are able to cause these
> faults with a simple shell script. The script executes a few - more or less
> arbitrarily selected - commands (du, lsmod, lusb, cp /boot/uImage /tmp/) in
> an endless loop and collects stderr outputs in a logfile. We usually start
> like 10 instances of the script in parallel (with &) and after a few
> minutes we find several reports about Illegal Instructions and/or
> Segmentation faults in the logfile.
Is there a correlation between the memory size the kernel gets reported and the
used memory devices soldered onto the board? ;)
> [...]
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-17 11:15 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
2014-01-20 7:49 ` Arno Euteneuer
2014-01-17 11:15 ` Jürgen Beisert [this message]
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=201401171215.46967.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--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