Date: Wed, 17 Jun 2015 10:43:27 +0300 From: Jukka Ukkonen <jau789@gmail.com> To: Tim Kientzle <tim@kientzle.com> Cc: Warner Losh <imp@bsdimp.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: RPI2 hanging during boot Message-ID: <4DC4E9D7-3751-4A6F-8727-61A6DB81FA9F@gmail.com> In-Reply-To: <80B5FC88-CA76-4A0D-AED5-15B5BA89607A@kientzle.com> References: <557EAE2F.3020307@gmail.com> <7F916FD0-7072-47B3-BBC5-A313CA731F81@bsdimp.com> <vczsh8.nq2ptj.ru4zhg-qmf@mx.google.com> <80B5FC88-CA76-4A0D-AED5-15B5BA89607A@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <tim@kientzle.com> 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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DC4E9D7-3751-4A6F-8727-61A6DB81FA9F>