Date: Thu, 20 May 2010 14:23:15 +0200 From: Matthias Reyelt <Matthias.Reyelt@brunel.de> To: Rafal Jaworowski <raj@semihalf.com> Cc: freebsd-arm@freebsd.org Subject: Re: files damaged on memory disk on Marvell Discovery 78100 Message-ID: <201005201423.18112.Matthias.Reyelt@brunel.de> In-Reply-To: <9E1BDCD0-CBE1-46D8-AECC-AE9E277C86B7@semihalf.com> References: <201005190820.00413.Matthias.Reyelt@brunel.de> <9E1BDCD0-CBE1-46D8-AECC-AE9E277C86B7@semihalf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I have changed the mount options for the memory disks and they work fine no= w.=20 I also got rid of regular crashes of the board :-) Are there other caveats in the virtual cache area, things that should be=20 avoided on the Marvell ARM? Matthias=20 Am Mittwoch 19 Mai 2010 12:29:52 schrieb Rafal Jaworowski: >=20 > On 2010-05-19, at 08:19, Matthias Reyelt wrote: >=20 > > I have observed a strange behaviour on the Marvell Discovery: > >=20 > > I have a memory disk for /etc and /opt: > > /dev/md0 on /etc (ufs, local) > > /dev/md1 on /opt (ufs, local) > >=20 > > When I copy files to that disk, which are larger than 0x1ffff (131071=20 bytes),=20 > > these files differ from the original. This occurs only when copying to = md.=20 > >=20 > > Kernel is: > > FreeBSD discovery1 8.0-STABLE FreeBSD 8.0-STABLE #0 r206836: Mon Apr 19= =20 > > 12:53:42 CEST 2010 =20 > > root@vbcspc12.bcs.brunel.local:/usr/obj/arm/root/ARM/8/sys/DB-78XXX arm > >=20 > > I had a look into the damaged file and found some excerpts from files=20 located=20 > > in /etc (which is also in RAM): > > ------------------------------------------------------------ > > passwd: compat > > passwd_compat: nis > > shells: files > > ----------------------------------------------------------------- > > ... > > ----------------------------------------------------------------- > > staff:*:20: > > sshd:*:22: > > smmsp:*:25: > > mailnull:*:26: > > guest:*:3-=EF=BF=BD=EF=BF=BD=EF=BF=BD=0F > > ------------------------------------------------------------------ > >=20 > > Looks as if the CPU has problems accessing the RAM. I have already chan= ged=20 the=20 > > RAM, so I don't think it's a hardware problem.=20 > >=20 > > Any idea? >=20 >=20 > Try turning off clustering on the filesystem(s). There was least one know= n=20 problem in this area leading to cache incoherency, see this thread for more= =20 details (and how-to):=20 http://lists.freebsd.org/pipermail/freebsd-arm/2008-December/001423.html >=20 > Rafal >=20 >=20 =2D-=20 Dr.-Ing. Matthias Reyelt Master Software Designer Brunel GmbH Bereich Communications Daimlerring 9 31135 Hildesheim Tel: +49 5121 1760 805 =46ax: +49 5121 1760 999 email: Matthias.Reyelt@brunel.de Internet: www.brunel.de Hauptsitz: Airport City, Hermann-K=C3=B6hl-Str. 1, 28199 Bremen Amtsgericht Bremen HRB 16935 General Manager: Johan Arie van Barneveld
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201005201423.18112.Matthias.Reyelt>