Date: Sat, 3 Mar 2018 18:53:15 -0500 From: Ryan Stone <rysto32@gmail.com> To: Konstantin Belousov <kostikbel@gmail.com> Cc: FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Panic in prison_alloc() on boot Message-ID: <CAFMmRNzt-hrVUrQME7d5fTybTSFctU4m4-upef6ZPKEndXQn%2Bg@mail.gmail.com> In-Reply-To: <CAFMmRNxCD0oCf-x0tRLvCs27AtpxxH2jq74yeB2HEEgZ=74wOg@mail.gmail.com> References: <CAFMmRNxCQpXCbC29=3bfmWmUxGmnVgZbxuoCesBEL3gBLwPuwg@mail.gmail.com> <20180212085852.GA94212@kib.kiev.ua> <CAFMmRNxCD0oCf-x0tRLvCs27AtpxxH2jq74yeB2HEEgZ=74wOg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
To close the loop on this, the root cause ended up being a mistake on my end. This system had a rather convoluted boot process, and as a result of that was loading a nullfs.ko built for a months-old kernel. This setup accidentally worked for some time, but I guess some recent change to struct thread changed the ABI, causing the old nullfs.ko to be incompatible and fail to boot. Sorry for the noise, Ryanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNzt-hrVUrQME7d5fTybTSFctU4m4-upef6ZPKEndXQn%2Bg>