From owner-freebsd-arm@FreeBSD.ORG Sun Feb 2 12:19:16 2014 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 ESMTPS id E56C8111; Sun, 2 Feb 2014 12:19:16 +0000 (UTC) Received: from turing.morphism.de (smtp.morphism.de [IPv6:2001:4178:4:204::25]) by mx1.freebsd.org (Postfix) with ESMTP id A3F721786; Sun, 2 Feb 2014 12:19:16 +0000 (UTC) Received: from localhost (moore.morphism.de [IPv6:2001:4178:4:202::136]) by turing.morphism.de (Postfix) with ESMTP id EDAC83DCC2; Sun, 2 Feb 2014 12:19:15 +0000 (UTC) Date: Sun, 2 Feb 2014 12:19:15 +0000 From: Markus Pfeiffer To: Ian Lepore Subject: Re: FreeBSD 10 on Dockstar (Marvell Kirkwood) Message-ID: <20140202121915.GC40214@moore.morphism.de> References: <20131231211054.GA90299@moore.morphism.de> <52C8DCCA.9050908@googlemail.com> <1388954952.1158.324.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/e2eDi0V/xtL+Mc8" Content-Disposition: inline In-Reply-To: <1388954952.1158.324.camel@revolution.hippie.lan> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-arm@FreeBSD.org, ssl.qlt@gmail.com, "army.of.root" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Markus Pfeiffer List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2014 12:19:17 -0000 --/e2eDi0V/xtL+Mc8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Dear all, (and Ian in particular) maybe also as a followup to "Dreamplug stable/10 usb - sd file transfer corruption error - cache related?", I tried to find out why my fsck produced so many bogus DUPS and did the same test, i.e. I dump/restored the entire filesystem from one USB device to another. And lo and behold I get blocks of 32 zeros in some files. My kernel is the 11-current DOCKSTAR kernel, and it contains the USB_ALIGN=32 line. I build using make -j 12 buildkernel TARGET_ARCH=ARM KERNCONF=DOCKSTAR I read things about clang-eabi, but I assume that is all the default configuration. If anyone has any hint as to where to even start debugging this I'd be more than happy. I gather it should be a cache coherency issue. Is it maybe a USB problem? I am at least vaguely familiar with the USB stack. Cheers, Markus P.S. if possible CC me, as I am not on the list. --/e2eDi0V/xtL+Mc8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (DragonFly) iQIcBAEBAgAGBQJS7jfDAAoJEBRHBRYBD4mPxgYP/0bLz5TObX6UVfifexsXTBiq PHHUyyeP22D4kpWLMMxwC5VXmvJ1Cnp1F0zvTtFNlWS/VypAjDs+UXXIiO+7zG2y zauVm8vgcdX7X8O/aqi6EhQPSMFBT4w9n7RpkdFStNySZYOVz2pAlePgw/yRm/zq mkrFixzv9bHSCsiLsFCcwlQSrRGtP++jGHy53euuNsnMm1DYBwrCZbrQoSm6bfsC hM2YF2HoQTaxdBqQFxDpBIzuqeQFW70hEaHFFiPhgUYv2HK4BJQNN6+Poznh5h9w 0VOg18KAW3YFRjbqfD/bC1dUzSm1cHWXCat/fXzSEPAbzBv64NADOmBOoqCJsm1W nIEUv2KtYdOVTkgdI3NGDTwKpVnMWH8B3IHSDvTI8l2eheNEQvF7jDRbRCEEIJwW jG5OoPrxlqpWeHIeRNoPZ5TWjbbpnuO4lnCVuAaYntRqCghiiq1dUatdYzEDgYwi HRL41jLSZfcmQD/oZk6vkm5jFXGH880szA35JPzm86kf1/ubslmYXeOzpBuH7v8O i7nph8VN/Vuln8Ux1fClSoIVZGW3umi8IjZEKDh8octMbkE2AB1FWdCmK58anLpg 09ChOy/icCw4G7/seEoKzmlRRKsl/D259Hee6g2hVnu6OA2WoUOUQVFxMbVW0KJp MaeTCJ3vbgx01fqu0F/V =A56X -----END PGP SIGNATURE----- --/e2eDi0V/xtL+Mc8--