From owner-freebsd-arm@FreeBSD.ORG Fri Mar 6 15:43:42 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 0D49F710 for ; Fri, 6 Mar 2015 15:43:42 +0000 (UTC) Received: from pmta1.delivery9.ore.mailhop.org (pmta1.delivery9.ore.mailhop.org [54.186.172.23]) by mx1.freebsd.org (Postfix) with ESMTP id DC3C9A17 for ; Fri, 6 Mar 2015 15:43:41 +0000 (UTC) Received: from smtp7.ore.mailhop.org (172.31.36.112) by pmta1.delivery1.ore.mailhop.org id hv75hk20r84s for ; Fri, 6 Mar 2015 15:43:20 +0000 (envelope-from ) Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp7.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YTuPY-0000kM-Mb; Fri, 06 Mar 2015 15:43:37 +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 t26FgpNp000917; Fri, 6 Mar 2015 08:42:51 -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/SL0AiDs+jGje34IdmiclZ Message-ID: <1425656571.51722.1.camel@freebsd.org> Subject: Re: crash on writing usbstick From: Ian Lepore To: Brett Wynkoop Date: Fri, 06 Mar 2015 08:42:51 -0700 In-Reply-To: <20150306022648.6f7b969d@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> <20150306022648.6f7b969d@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: Fri, 06 Mar 2015 15:43:42 -0000 On Fri, 2015-03-06 at 02:26 -0500, Brett Wynkoop wrote: > Greeting- > > I just had a thought, while trying to crash my BBone again. Back when > I started with BSD on PDP-11/70 we had to order special disk packs for > BSD that were certified error free because Unix in those days had no > way to map out bad blocks and could crash on hitting bad blocks. > > When we moved to using BSD on Pyramid and Sun boxes there were > utilities to map out bad blocks. I do not remember what it was under > OS/X, but on Sun OS 3.x and on it is of course part of the format > command. As I recall we used to have utilities for bad block mapping > in FreeBSD back in the 2.x and 3.x days. Sometime around the 4.x or > 5.x days drive makers started to do bad block mapping with the firmware > on the drives. > > Could it be that the whole issue here is that I am running into disk > faults on the flash disks and the flash drives have no way to map the > blocks out such as modern rotating drives do with SMART and such? > > I have done a bit of man -k searching but I have not found anything for > mapping out bad blocks in 11-current. > > At the moment I am just over 1/2 way in copying /usr/ports > to /export/ports with no crash yet but a bunch of > > aintc0: Spurious interrupt detected (0xffffffff) > aintc0: Spurious interrupt detected (0xffffffff) > aintc0: Spurious interrupt detected (0xffffffff) > > messages on the console. > > -Brett > Bad block remapping is handled by the microcontroller in the usb device. These panics are not caused by IO errors, if they were you'd see stuff like this on the console before the panic... g_vfs_done():da0p1[WRITE(offset=1674510336, length=131072)]error = 6 -- Ian