Date: Mon, 13 Sep 2021 21:33:15 +0200 From: Guido Falsi via freebsd-current <freebsd-current@freebsd.org> To: Ryan Stone <rysto32@gmail.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: recent head having significantly less "avail memory" Message-ID: <f365f896-1986-02d2-f1d9-ed6de9ee2b6f@madpilot.net> In-Reply-To: <CAFMmRNxg1PhLujYikjU7qxRpWtnXVshUx4W_5e6ZNWKZhrOhMQ@mail.gmail.com> References: <4c990632-868a-2393-291b-fe7e2bc1974f@madpilot.net> <YT%2BFiWtUKZuZIbIb@kib.kiev.ua> <6ea7c339-1b8e-9764-4d28-5a98756e05ff@madpilot.net> <CAFMmRNxg1PhLujYikjU7qxRpWtnXVshUx4W_5e6ZNWKZhrOhMQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/09/21 20:17, Ryan Stone wrote: > On Mon, Sep 13, 2021 at 2:13 PM Guido Falsi via freebsd-current > <freebsd-current@freebsd.org> wrote: >> I'm not sure how to get the verbose data for the old boot, since I've >> been unable to revert the machine to the old state. I'll try anyway though. > > Do you have physical access to the machine? It might be easiest to > grab a snapshot image, stick it on a USB drive and boot from that. > I definitely have physical access, it's my desktop, laptop and build machines. First thing I'm doing is disable cron job removing old zfs snapshots, so state is not lost. Since this is involving only UEFI, loader and kernel, I've recovered the old parts and now I have the machine reporting the usual amount of memory, so I should be able to extract the requested data and post it shortly. Thanks for your help anyway! -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f365f896-1986-02d2-f1d9-ed6de9ee2b6f>