From owner-freebsd-arm@FreeBSD.ORG Wed Mar 5 11:48:25 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E920160A for ; Wed, 5 Mar 2014 11:48:25 +0000 (UTC) Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AD2AFD81 for ; Wed, 5 Mar 2014 11:48:25 +0000 (UTC) Received: by mail-ob0-f181.google.com with SMTP id wp4so866349obc.40 for ; Wed, 05 Mar 2014 03:48:19 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=91aypn5KV6RR2oRDQwJKOsKqzbzNflf5FrMeNuZzTMw=; b=DDZCiQIYOzWpu+8LOXdrA8h3wWFFesQnrlo/8ttlWykBId76hCC8msXCLvGD2Ra1fh V4iw93UG/mCMIV6/tBAR4QkotSg0xfFnX/03QS6sO0hx5W2+MZA6LgpWcmZtOY+m7hUQ 2K6eyTCBzWu26tyyla1BNrFMZCVgR6lzRmRtR2enE4p1lTx+UXbQ4oMVlmHdcn9f/p/0 j8MfFrVf+U2+RkBg0ejK24/Yhq4oiJGyvFuZgbEglcLIIOhqrxfEu1l8jeUT2hkS/gzk 3tRrpQaVi8RuZ9x6K9L4qHVroGuOMsF5aLDTuUQGZGXYaMHM8oWjABmMucyZNwCSn6+G AJxQ== X-Gm-Message-State: ALoCoQnyp027O7dgz8Rsc/IimNaoDWD8gf9qkyyavTCkLR6oCt9yUZvHpKLleXUgMrPRz/ZZma8m MIME-Version: 1.0 X-Received: by 10.182.112.130 with SMTP id iq2mr1170657obb.57.1394020099395; Wed, 05 Mar 2014 03:48:19 -0800 (PST) Received: by 10.182.165.167 with HTTP; Wed, 5 Mar 2014 03:48:19 -0800 (PST) X-Originating-IP: [2001:44b8:31b0:aa00:c685:8ff:fe35:3e2d] In-Reply-To: References: <87ob2gxfg0.fsf@gmail.com> <1392997297.1145.88.camel@revolution.hippie.lan> <53077971.8060406@gmail.com> Date: Wed, 5 Mar 2014 22:48:19 +1100 Message-ID: Subject: Re: Beaglebone Black: crash during portsnap extract From: Jason Birch To: freebsd-arm Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2014 11:48:26 -0000 I'm not sure the underlying problem is solved here -- I encountered it on r262372 when compiling lang/perl5.16 overnight, and I see emails dating back to at least September 2013 on r255438, which followed with a discussion on what you can possibly do to recover in these scenarios. In the mean time, I might purchase a faster SD card for use with my BeagleBone Black as a cheap (effortwise) work-around, as I'm using a spare Class 4 I had lying around. On Mon, Feb 24, 2014 at 11:13 PM, Jason Birch wrote: > Henryk notes that this doesn't occur when just copying the tree around -- >> although that'll be many smaller files instead of one big one. I wonder if >> it's specifically happening in conjunction with bsdtar -- I'll try and >> contrive a testcase later this afternoon. > > > I can't trigger this as a non-privileged user. I can reliably trigger this > by a simple `tar xf /var/db/portsnap/.tgz` as root. > > I'm taking r262372 for a spin now (Which of course includes your r261983), > and have been able to successfully extract the ports tree as root without > being dumped into ddb. Though... I have been sitting here waiting for the > snapshot verification for quite a while, but that's another story. The only > thing untoward I see is that UFS lock order reversal... > > lock order reversal: > 1st 0xc2f73394 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2101 > 2nd 0xcd25c3c8 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:262 > 3rd 0xc2f93934 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2101 > > ... but I think that's well known at this point and isn't a cause for my > concern. > > Thanks Ian! >