Re: nvmm-induced panic on -current

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

It happens with any of my virtual machines, immediately after starting
qemu-nvmm. I can get a dump if it might be useful.

On Sun, 5 Jan 2020 at 14:17, Chavdar Ivanov <ci4ic4%gmail.com@localhost> wrote:
>
> Hi,
>
> I just got:
> .....
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] panic: fpudna from
> kernel, ip 0xffffffff80226c3f, trapframe 0xffffdc81fab42c80
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] cpu0: Begin traceback...
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] vpanic() at netbsd:vpanic+0x178
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] snprintf() at netbsd:snprintf
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] fpu_set_default_cw() at
> netbsd:fpu_set_default_cw
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] Xtrap07() at netbsd:Xtrap07+0xbd
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] nvmm_ioctl() at
> nvmm:nvmm_ioctl+0xec
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] sys_ioctl() at
> netbsd:sys_ioctl+0x59e
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] syscall() at netbsd:syscall+0x299
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] --- syscall (number 54) ---
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] 73188eb8199a:
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7533581] cpu0: End traceback...
> Jan  5 14:07:04 ymir /netbsd:
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7649742] dumping to dev 168,2
> (offset=8, size=5225879):
> Jan  5 14:07:04 ymir /netbsd: [ 59319.7649742] dump failed:
> insufficient space (7221248 < 11753276)
> ....
>
> on
>
> NetBSD 9.99.33 (GENERIC) #17: Sat Jan  4 18:16:34 GMT 2020
>         sysbuild@ymir:/home/sysbuild/amd64/obj/home/sysbuild/src/sys/arch/amd64/compile/GENERIC
>
> starting one of my qemu-nvmm virtual machines - Windows 10 32-bit -
> which used to work rather well, but I haven't started it for several
> weeks, so am not sure when the break has happened.
>
> Chavdar
>
>
>
> --
> ----



-- 
----