Date: Fri, 27 Sep 2019 07:43:31 -0600 From: Alan Somers <asomers@freebsd.org> To: Andriy Gapon <avg@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: panic: Unregistered use of FPU in kernel Message-ID: <CAOtMX2hd00OSUNTuYzXKgVZKSOb03iQNN4SE7ZABGjGnMJeAbw@mail.gmail.com> In-Reply-To: <6f694ce3-ad1d-ce90-addd-ffac98b5e957@FreeBSD.org> References: <CAOtMX2gLM8uWuQEz3jq2S3i7BfhUq=y6EH4MCchdJDmnzRqGsA@mail.gmail.com> <6f694ce3-ad1d-ce90-addd-ffac98b5e957@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 27, 2019 at 5:50 AM Andriy Gapon <avg@freebsd.org> wrote: > 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. > Yeah, it's running in KVM/QEMU on an Ubuntu 18.04 host. The only thing slightly unusual is the Kaby Lake CPU.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2hd00OSUNTuYzXKgVZKSOb03iQNN4SE7ZABGjGnMJeAbw>