Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Alan Somers
You're right, cem. gdb and ddb show the same data. Here it is from gdb: 0x8113b30e : 0xf2 0x48 0x0f 0x38 0xf1 0xde 0xf2 0x48 0x8113b316 : 0x0f 0x38 0xf1 0xc7 0x48 0x8b 0x32 0xf2 0x8113b31e : 0x4c 0x0f 0x38 0xf1 0xde 0x48 0x8d 0x72 0x8113b326 : 0x08 0x48 0x81 0xc2 0

Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Konstantin Belousov
On Thu, Sep 26, 2019 at 02:12:21PM -0600, Alan Somers wrote: > On Thu, Sep 26, 2019 at 11:29 AM Konstantin Belousov > wrote: > > > On Thu, Sep 26, 2019 at 11:20:51AM -0600, Alan Somers wrote: > > > On Thu, Sep 26, 2019 at 11:02 AM Konstantin Belousov < > > kostik...@gmail.com> > > > wrote: > > >

Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Conrad Meyer
This kinda just looks like ddb doesn't know how to disassemble crc32q? Which might not be too surprising. Note that it also truncates the qword constant in "add" at +167/+0xa7. That one isn't corruption; just a DDB bug. Can you print the faulting %rip and dump a few bytes at that address in both

Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Alan Somers
On Thu, Sep 26, 2019 at 11:29 AM Konstantin Belousov wrote: > On Thu, Sep 26, 2019 at 11:20:51AM -0600, Alan Somers wrote: > > On Thu, Sep 26, 2019 at 11:02 AM Konstantin Belousov < > kostik...@gmail.com> > > wrote: > > > > > On Thu, Sep 26, 2019 at 09:45:43AM -0600, Alan Somers wrote: > > > > Th

Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Konstantin Belousov
On Thu, Sep 26, 2019 at 11:20:51AM -0600, Alan Somers wrote: > On Thu, Sep 26, 2019 at 11:02 AM Konstantin Belousov > wrote: > > > 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

Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Alan Somers
On Thu, Sep 26, 2019 at 11:02 AM Konstantin Belousov wrote: > 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

Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Lev Serebryakov
On 26.09.2019 20:02, Konstantin Belousov wrote: >> 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 ar

Re: panic: Unregistered use of FPU in kernel

2019-09-26 Thread Konstantin Belousov
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 >

panic: Unregistered use of FPU in kernel

2019-09-26 Thread Alan Somers
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 th

Re: Booting anything after r352057 kills console - additional info

2019-09-26 Thread Thomas Laus
On 2019-09-25 17:51, Thomas Laus wrote: > I was able to mount my zfs filesystem r+w and added the rc_debug="YES" > to my rc.conf. The additional debug messages were written to the beadm > boot environment /var/log/messages. Since the computer locked up, I was > unable to read this log and email t