Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 May 2010 11:51:38 -0500
From:      Mark Tinguely <marktinguely@gmail.com>
To:        Rafal Jaworowski <raj@semihalf.com>
Cc:        Matthias Reyelt <Matthias.Reyelt@brunel.de>, freebsd-arm@freebsd.org
Subject:   Re: files damaged on memory disk on Marvell Discovery 78100
Message-ID:  <4BF4171A.3050706@gmail.com>
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
Rafal Jaworowski wrote:
> On 2010-05-19, at 08:19, Matthias Reyelt wrote:
>
>   
>> I have observed a strange behaviour on the Marvell Discovery:
>>
>> I have a memory disk for /etc and /opt:
>> /dev/md0 on /etc (ufs, local)
>> /dev/md1 on /opt (ufs, local)
>>
>> When I copy files to that disk, which are larger than 0x1ffff (131071 bytes), 
>> these files differ from the original. This occurs only when copying to md. 
>>
>> Kernel is:
>> FreeBSD discovery1 8.0-STABLE FreeBSD 8.0-STABLE #0 r206836: Mon Apr 19 
>> 12:53:42 CEST 2010    
>> root@vbcspc12.bcs.brunel.local:/usr/obj/arm/root/ARM/8/sys/DB-78XXX  arm
>>
>> I had a look into the damaged file and found some excerpts from files located 
>> in /etc (which is also in RAM):
>> ------------------------------------------------------------
>> passwd: compat
>> passwd_compat: nis
>> shells: files
>> -----------------------------------------------------------------
>> ...
>> -----------------------------------------------------------------
>> staff:*:20:
>> sshd:*:22:
>> smmsp:*:25:
>> mailnull:*:26:
>> guest:*:3-���
>> ------------------------------------------------------------------
>>
>> Looks as if the CPU has problems accessing the RAM. I have already changed the 
>> RAM, so I don't think it's a hardware problem. 
>>
>> Any idea?
>>     
>
>
> Try turning off clustering on the filesystem(s). There was least one known problem in this area leading to cache incoherency, see this thread for more details (and how-to): http://lists.freebsd.org/pipermail/freebsd-arm/2008-December/001423.html
>
> Rafal
>   
Hmmm.

The Discovery  must have PIPT  caches? (The 
S_MV76100_78100_78200_OpenSource.pdf  doc mentions
32KB/4 way I/D cache; 128-256KB/8 way L2 caches, so I assume from that 
configuration, they must be PIPT).
I don't have access to the MV internal cache documents.

Is the L2 enabled?

Probably off topic: Does this have an active PCI express? I just noticed 
the note for the SlvWrSpltCnt bit in the PCI
Express Window1-4 Control Registers.

--Mark Tinguely.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BF4171A.3050706>