From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
From: =?iso-8859-1?q?J=FCrgen_Beisert?= <jbe@pengutronix.de>
Date: Fri, 17 Jan 2014 14:20:14 +0100
References: <49BD654B8E52F64BBC06DF3F86638DFAF59FF7@MSE1MUC.toptica.com>
	<201401171215.46967.jbe@pengutronix.de>
	<49BD654B8E52F64BBC06DF3F86638DFAF5A035@MSE1MUC.toptica.com>
In-Reply-To: <49BD654B8E52F64BBC06DF3F86638DFAF5A035@MSE1MUC.toptica.com>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <201401171420.14305.jbe@pengutronix.de>
Subject: Re: [ptxdist] sporadic crashes of shell commands
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=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


On Friday 17 January 2014 13:50:45 Arno Euteneuer wrote:
> Hi J=FCrgen,
>
> > [...]
> > Is there a correlation between the memory size the kernel gets reported
> > and the used memory devices soldered onto the board? ;)
> >
> > [...]
>
> I hope there is a very strong correlation ;-)

:)

> We have 256MB DDR2 RAM and 512MB NAND flash and get the following:
>
> root@dlcpro:~ cat /proc/meminfo
> MemTotal:         235876 kB
> MemFree:          169852 kB
> Buffers:               0 kB
> Cached:            27988 kB
> SwapCached:            0 kB
> Active:            15648 kB
> Inactive:          22560 kB
> Active(anon):      10300 kB
> Inactive(anon):      104 kB
> Active(file):       5348 kB
> Inactive(file):    22456 kB
> Unevictable:           0 kB
> Mlocked:               0 kB
> SwapTotal:             0 kB
> SwapFree:              0 kB
> Dirty:                 0 kB
> Writeback:             0 kB
> AnonPages:         10248 kB
> Mapped:            29924 kB
> Shmem:               184 kB
> Slab:              11100 kB
> SReclaimable:       4848 kB
> SUnreclaim:         6252 kB
> KernelStack:         544 kB
> PageTables:          336 kB
> NFS_Unstable:          0 kB
> Bounce:                0 kB
> WritebackTmp:          0 kB
> CommitLimit:      117936 kB
> Committed_AS:      73872 kB
> VmallocTotal:     761856 kB
> VmallocUsed:       27740 kB
> VmallocChunk:     639888 kB
>
> This looks very much the same with either of the kernels, independent of
> the used toolchain. For me this looks ok, doesn't it? (Although I must
> admit I'm not really sure what VmallocTotal tells me and whether it is
> correct to be so large. Looks like RAM + Flash?)

Looks okay in your case. Some time ago we faced similar failures when the =

system starts to grow its memory consumption. Until it uses the really amou=
nt =

of memory everything was fine, and when it hits the border to the non exist=
ing =

memory unpredictable things happend similar to yours.

Regards,
Juergen

-- =

Pengutronix e.K. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0| Juergen Beisert =A0 =A0 =A0 =A0 =A0 =A0 |
Linux Solutions for Science and Industry =A0 =A0 =A0| http://www.pengutroni=
x.de/  |

-- =

ptxdist mailing list
ptxdist@pengutronix.de