Date: Tue, 27 Jun 2017 11:16:47 -0500 From: Eric van Gyzen <eric@vangyzen.net> To: Michael Jung <mikej@mikej.com>, freebsd-current@freebsd.org Subject: Re: r320358 panics immediately on boot / AMD64-GENERIC kernel Message-ID: <728a734d-6d3e-4b29-2e7a-cfe5877eedff@vangyzen.net> In-Reply-To: <78b111f8c0c26a08d204d1ba16c55df1@mikej.com> References: <EE44D551-B078-49FF-8498-7C0369598301@paymentallianceintl.com> <4edb3e720c071385f8a6555c89116530@mikej.com> <939f19bd428b232515463436995da4b7@mikej.com> <78b111f8c0c26a08d204d1ba16c55df1@mikej.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/27/2017 11:09, Michael Jung wrote: > Screen image with backtrace > > https://pasteboard.co/dZRVG5Uo.jpg > > > After upgrading from 318959 to 320358 I immediately get the attached panic. > > This is AMD64 / GENERIC kernel. > > /boot/loader.conf is empty. > > The system boots off a UFS2 partition. > > This is a virtual guest and I do currently have a serial cable. > > Short of figuring out how to virtualize a serial console from a ESXi > guest is > there any more information I can provide? Someone else hit this. Removing the contents of /usr/obj and rebuilding fixed it for him. Apparently, some of the objects didn't get rebuilt, as needed. Eric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?728a734d-6d3e-4b29-2e7a-cfe5877eedff>