From owner-freebsd-arm@FreeBSD.ORG Fri Oct 25 21:38:27 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9DA8AA59 for ; Fri, 25 Oct 2013 21:38:27 +0000 (UTC) (envelope-from ssl.qlt@gmail.com) Received: from mail-ea0-x241.google.com (mail-ea0-x241.google.com [IPv6:2a00:1450:4013:c01::241]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 26A732389 for ; Fri, 25 Oct 2013 21:38:27 +0000 (UTC) Received: by mail-ea0-f193.google.com with SMTP id o10so324455eaj.0 for ; Fri, 25 Oct 2013 14:38:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=SQkVYztS5QO7Mw+vUjMxK4SsmQAIZg2JqQ+gHo7G9SA=; b=ATWK42RiSExJm93anzORieCunn17SYXMnUHtd0JywNV1pzdYDgQlci8ijsnPZM9Coz UoTp5yQ29hTPAhvqU+D79YycK1i9m3vNcZhFev3hZMc+uV0XgUUP7YCAW+BRlsmfUgQM tehiMf9YXPKaPp86QJ5Ysv+ffj4WnhyXD12fruUHJs4dN0fVy8HFiAYm4N/fYAaP/M+u RfeXe7x56L3UYrH3s8cmgTAD5b+Ru3D10hKlbvGB4xrB1OFW7rwP1EW7igePBLr7xI4q kMm8QdmIJ1ppHH0JvFhwKGjjPEoAhWhYJYvL1Ct4sPHBFiU2x8h/FeQSpcqojhbGdb6y H3nA== MIME-Version: 1.0 X-Received: by 10.204.168.197 with SMTP id v5mr1852bky.24.1382737104644; Fri, 25 Oct 2013 14:38:24 -0700 (PDT) Received: by 10.204.231.209 with HTTP; Fri, 25 Oct 2013 14:38:24 -0700 (PDT) In-Reply-To: References: <1382734990.1170.132.camel@revolution.hippie.lan> Date: Fri, 25 Oct 2013 14:38:24 -0700 Message-ID: Subject: Fwd: Dreamplug stable/10 usb - sd file transfer corruption error - cache related? From: Steven Lee To: freebsd-arm@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Oct 2013 21:38:27 -0000 ---------- Forwarded message ---------- From: Steven Lee Date: Fri, Oct 25, 2013 at 2:37 PM Subject: Re: Dreamplug stable/10 usb - sd file transfer corruption error - cache related? To: Ian Lepore Ian, thanks for your reply. I am using the DREAMPLUG-1001 stock kernel config, and you are right the internal sd card shows up as a usb device, /dev/da0. As I mentioned, I tried modifying pmap.c as per one of your suggestions to an earlier poster / problem, but it didn't seem to help the issue. I changed the pmap_pte_init_arm10() function to look like the pmap_pte_init_arm9() function. Any other thoughts about things to try? Since it seems like this is a regression between 9 and 10, are you aware of any specific cache related changes to the usb driver between the branches? - Steve On Fri, Oct 25, 2013 at 2:03 PM, Ian Lepore wrote: > On Fri, 2013-10-25 at 13:37 -0700, Steven Lee wrote: > > Hello, > > > > In the process of upgrading my Dreamplug from the stable/9 branch to the > > stable/10 branch, I have run into a fairly > > significant file corruption problem. The steps that create this problem > > are as follows: > > > > 1. Cross-compile the kernel and buildworld from the stable/10 branch on a > > separate host. > > 2. Install the kernel and installworld on a usb stick drive > > 3. Boot the Dreamplug from the usb drive > > > > There are no problems that show up to this point, the Dreamplug boots > with > > no errors. > > > > 4. Copy the kernel from the usb drive to the internal sd card > > 5. Copy the root filesystem from the usb drive to the internal sd card > > using (dump | restore) > > > > It is at step 5 that the error manifests itself, as I found that > > approximately 20 shell scripts in the /etc/rc.d directory > > had been randomly corrupted with strings of null characters (in groups of > > 32). I assume that the rest of the file system > > was compromised in a similar fashion. The bug is repeatable, however the > > corruption is somewhat random, so > > each time different files are corrupted in different places. > > > > When I followed the exact same steps from the stable/9 branch, the > problem > > did not occur, so there is clearly some > > type of regression error between the 9 and 10 branches. > > > > After searching through the arm mailing list, I attempted to work around > > the problem by: > > - mounting the file systems with -o noclusterr -o noclusterrw > > - mounting the file systems with -o sync > > - as per comments on bug arm/158950, attempted to modify the pmap.c > > functions to change the cache from > > write-back mode to write-through mode > > > > but all of these attempts were ineffective. > > > > Given that I am relatively new to FreeBSD, I was hoping to get any > insights > > as to any next steps that might make > > sense in terms of either working around the problem, narrowing down the > > bug, or any obvious rookie mistakes I > > am making before I give up and revert back to the 9 branch. > > > > Thanks for your help! > > > > Regards, > > On my dreamplug (model 1001) both the internal and external sd cards are > actually usb devices (they show up as /dev/da0 and da1, not mmcsd0/1). > I'm not sure if that's true on all models or not. > > Are you using the stock kernel config (DREAMPLUG-1001)? If not, have > you got "option USB_HOST_ALIGN=32" in your kernel config? > > Corruption in 32 byte chunks is almost always partial cacheline flush > problems, but I haven't seen that happen on dreamplug for a long time > (and when I did see it, it was with a sata drive). > > -- Ian > >