Date: Fri, 27 Sep 2019 14:50:12 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Alan Somers <asomers@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: panic: Unregistered use of FPU in kernel Message-ID: <6f694ce3-ad1d-ce90-addd-ffac98b5e957@FreeBSD.org> In-Reply-To: <CAOtMX2gLM8uWuQEz3jq2S3i7BfhUq=y6EH4MCchdJDmnzRqGsA@mail.gmail.com> References: <CAOtMX2gLM8uWuQEz3jq2S3i7BfhUq=y6EH4MCchdJDmnzRqGsA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 26/09/2019 18:45, Alan Somers wrote: > The latest VM snapshot (FreeBSD-13.0-CURRENT-amd64-20190920-r352544.qcow2) > instapanics on boot: > > panic: Unregistered use of FPU in kernel > > stack trace: > ... > sse42_crc32c > readsuper > ffs_sbget > g_label_ufs_taste_common > g_label_taste > g_new_provider_event > g_run_events > fork_exit > ... > > Has anybody touched this area recently? I'll try to narrow down the commit > range. Given the qcow2 image, is this in a VM? What hypervisor? It could be a bug there. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6f694ce3-ad1d-ce90-addd-ffac98b5e957>