From owner-freebsd-arm@FreeBSD.ORG Fri Mar 6 02:18:26 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 641297D7; Fri, 6 Mar 2015 02:18:26 +0000 (UTC) Received: from wa3yre.wynn.com (wa3yre.wynn.com [199.89.147.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B298BBFA; Fri, 6 Mar 2015 02:18:23 +0000 (UTC) Received: from ivory.wynn.com (mail.wynn.com [199.89.147.3]) (authenticated bits=0) by wa3yre.wynn.com (8.14.3/8.12.6) with ESMTP id t262IFV8064031; Thu, 5 Mar 2015 21:18:16 -0500 (EST) (envelope-from freebsd-arm@wynn.com) Date: Thu, 5 Mar 2015 21:18:13 -0500 From: Brett Wynkoop To: Ian Lepore , freebsd-arm@freebsd.org Subject: Re: crash on writing usbstick Message-ID: <20150305211813.6de87a74@ivory.wynn.com> In-Reply-To: <1425595999.28798.11.camel@freebsd.org> 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> <1425595999.28798.11.camel@freebsd.org> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; x86_64-apple-darwin10.8.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Fri, 06 Mar 2015 02:18:26 -0000 On Thu, 05 Mar 2015 15:53:19 -0700 Ian Lepore wrote: > 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 > > Yeah I see those spurious interrupt messages as well on many of my copy attempts. Let me know when you check your code in and I will update my sources and rebuild to see what we get. My exact setup is a BeagleBone with external power connected via the coaxial power port and also powered via USB from the FreeBSD 7 box it is connected to for console access. The current USB stick is directly plugged into the PI. It is a Staples 16GB Relay. I have had the same exact results with Verbatim and Emtec. root@beaglebone:~ # uname -a FreeBSD beaglebone.wynn.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r279219: Sun Mar 1 03:31:54 EST 2015 wynkoop@beaglebone.wynn.com:/usr/src/sys/arm/compile/BB-BEW arm root@beaglebone:~ # The only thing in my kernel not in the generic BB kernel is the addition of these two options: options GEOM_RAID # Soft RAID functionality. options GEOM_LABEL # Provides labelization I will note though that before I put these options and I was running the Generic BeagleBone kernel I had the exact same issue. I added the above because I had some thoughts of maybe running raid, and I prefer to mount by label names. -Brett -- wynkoop@wynn.com http://prd4.wynn.com/wynkoop/pgp-keys.txt 917-642-6925 929-272-0000 Amendment IV The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no warrants shall issue, but upon probable cause, supported by oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized.