Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Sep 2019 20:02:41 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Alan Somers <asomers@freebsd.org>
Cc:        FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   Re: panic: Unregistered use of FPU in kernel
Message-ID:  <20190926170241.GG44691@kib.kiev.ua>
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 Thu, Sep 26, 2019 at 09:45:43AM -0600, 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.

Start with disassembling the faulting instruction.  I suspect that somehow
vital compiler switches like -mno-sse got omitted in the build.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190926170241.GG44691>