From owner-freebsd-arm@FreeBSD.ORG Thu Mar 5 22:53:33 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1677467 for ; Thu, 5 Mar 2015 22:53:33 +0000 (UTC) Received: from pmta1.delivery10.ore.mailhop.org (pmta1.delivery10.ore.mailhop.org [54.149.36.10]) by mx1.freebsd.org (Postfix) with ESMTP id BA6F869C for ; Thu, 5 Mar 2015 22:53:33 +0000 (UTC) Received: from smtp4.ore.mailhop.org (172.31.18.134) by pmta1.delivery1.ore.mailhop.org id hv3f5m20r844 for ; Thu, 5 Mar 2015 22:53:07 +0000 (envelope-from ) Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp4.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YTedv-00018H-JC; Thu, 05 Mar 2015 22:53:23 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t25MrJPO099301; Thu, 5 Mar 2015 15:53:19 -0700 (MST) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1/8dQuKp/8+pHW85TVtB9BS Message-ID: <1425595999.28798.11.camel@freebsd.org> Subject: Re: crash on writing usbstick From: Ian Lepore To: Brett Wynkoop Date: Thu, 05 Mar 2015 15:53:19 -0700 In-Reply-To: <20150305153421.2e2bca98@ivory.wynn.com> References: <20150301041855.5352663e@ivory.wynn.com> <20150301144653.63b38cdf@ivory.wynn.com> <20150301184456.7b5e6487@ivory.wynn.com> <1DC8221F-64EA-418C-8CE5-5FFA4F3DBC64@bsdimp.com> <20150301203244.55578413@ivory.wynn.com> <20150305064318.2f35f2c0@ivory.wynn.com> <1425567301.3471.6.camel@freebsd.org> <20150305153421.2e2bca98@ivory.wynn.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Mar 2015 22:53:34 -0000 On Thu, 2015-03-05 at 15:34 -0500, Brett Wynkoop wrote: > On Thu, 05 Mar 2015 07:55:01 -0700 > Ian Lepore wrote: > > > I spent some time yesterday trying to reproduce this, and couldn't. > > The only usb thumb drive I have handy right now is 4gb, which isn't > > quite big enough to hold the entire ports tree, but using your tar|tar > > incantation it will run to the point where the destination filesystem > > is full without any errors; I did that twice. > > > > You didn't say what you were using as a source for the copy (sdcard, > > nfs, etc). I was using an nfs mount as source, which on BBB means > > that usb is involved as both the source and destination. > > > > Hmm, I just realized the ports tree I'm copying includes .svn, no > > wonder it's so big. I'll bet if I exclude that from the copy it'll > > run to completion. > > Greeting- > > Would you like access to my BB via ssh and also access to it's console > via ssh? > > I have had the same results with several usb sticks, but all of them > have been at least 16GB. I am also swapping to the current USB stick > on a swap partation, but I have had the same results on this stick and > others without swapping to it. > > /usr/ports is on the root fs on the sd card. > I got my ports tree onto sdcard then copied it to the usb stick using the tar|tar command, still can't reproduce the problem at all. Nobody else has reported any beaglebone IO-related panics or errors for months either. I wonder what's different about your setup? (Nice side effect... doing the nfs->usb copy created hundreds of spurious interrupt messages, I've never been able to reproduce them reliably before. I think I've got them fixed now; tests still running.) -- Ian