From owner-freebsd-arm@FreeBSD.ORG Wed Jun 17 12:51:17 2015 Return-Path: Delivered-To: freebsd-arm@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E2486572 for ; Wed, 17 Jun 2015 12:51:17 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 52F28842 for ; Wed, 17 Jun 2015 12:51:17 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by laka10 with SMTP id a10so32309864lak.0 for ; Wed, 17 Jun 2015 05:51:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=X7epVub1uVEiNjnkJRTnUXpOn0NCx+DIyJCeJZ6jQdI=; b=KeqAZKG4xef8d8hhKa5GiHrbvIpaL0oiGwPr/41PRUrtR/9thNKPkSEKsyIY34ZPEt MIBSdM4Jpz+87oEK5s7EaokEicZCVCr6euexvflYB6ny8A9NJxvYJpsDrOdlsmlNLD+D XPd5iLa9mI/QjYZx9y8XYtm7TvAkCu89ZwjChPwOXIG6/7/iqcP74Hr4cHgo9TLP1eXD ALRuqyTzDs5cv+wO7JczhhfA+GyPUHrExnOwH2NxFLvn+PlvWZ/qTUqCsfbl/wnLAmVe TZCxv9sIH6TeJ3UwIz/Kwv4atEebAhAqtVWsb11v4pwjnVhNTFuV8mPa2Ki+fOAP7GjI 7N/Q== X-Received: by 10.112.72.2 with SMTP id z2mr6208117lbu.39.1434527008702; Wed, 17 Jun 2015 00:43:28 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-163.nblnetworks.fi. [83.145.205.163]) by mx.google.com with ESMTPSA id fj10sm782930lbc.29.2015.06.17.00.43.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 17 Jun 2015 00:43:28 -0700 (PDT) Mime-Version: 1.0 (1.0) Subject: Re: RPI2 hanging during boot From: Jukka Ukkonen X-Mailer: iPad Mail (12F69) In-Reply-To: <80B5FC88-CA76-4A0D-AED5-15B5BA89607A@kientzle.com> Date: Wed, 17 Jun 2015 10:43:27 +0300 Cc: Warner Losh , freebsd-arm Message-Id: <4DC4E9D7-3751-4A6F-8727-61A6DB81FA9F@gmail.com> References: <557EAE2F.3020307@gmail.com> <7F916FD0-7072-47B3-BBC5-A313CA731F81@bsdimp.com> <80B5FC88-CA76-4A0D-AED5-15B5BA89607A@kientzle.com> To: Tim Kientzle Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jun 2015 12:51:18 -0000 Right, and if swaplate fails for whatever reason to release some existing swap area before releasing the file systems and devices, what will happen then? Esp. devices living on top of file systems, like md, may create a kind of a chicken and egg problem. The proper means from my point of view would be the kernel itself flushing the swap areas and revoking them before letting go of the underlying device or file system. Maybe the kernel even does this and I simply failed to notice where it is done. I don't know really. I am just beating the bushes here, because it would take quite some time for me to read through the source in detail enough to convince myself about what will happen and when, where, and why. --jau Sent from my iPad > On 17 Jun 2015, at 09:44, Tim Kientzle wrote: > > >> On Jun 16, 2015, at 10:27 PM, jau789@gmail.com wrote: >> >> Maybe >> the same problem with unreleased swap space which I suspect >> as the culprit to my unbootable ufs2 on an SD card applies to >> any and all swap spaces, even those mentioned in the fstab. > > Swap spaces mentioned in the fstab are automatically > released on shutdown by /etc/rc.d/swaplate. > > Tim >