[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-current-users
Subject:    Panic on -current, apparently NFS-related
From:       Chavdar Ivanov <ci4ic4 () gmail ! com>
Date:       2020-05-31 22:01:02
Message-ID: CAG0OUxiH1rzzaE_-ynzUvPhcwn-=jE7r-hKiNfKB7hetdSFJ2g () mail ! gmail ! com
[Download RAW message or body]

Hi,

On yesterday's -current amd64 I just got:
...

crash$ crash -M netbsd.17.core -N netbsd.17
Crash version 9.99.64, image version 9.99.64.
crash: _kvm_kvatop(0)
Kernel compiled without options LOCKDEBUG.
System panicked: Bad nfs svc reply
Backtrace from time of crash is available.
crash> bt
_KERNEL_OPT_NARCNET() at 0
_KERNEL_OPT_ACPI_SCANPCI() at _KERNEL_OPT_ACPI_SCANPCI
sys_reboot() at sys_reboot
vpanic() at vpanic+0x15b
snprintf() at snprintf
do_nfssvc() at do_nfssvc+0x1631
syscall() at syscall+0x26e
--- syscall (number 155) ---
syscall+0x26e:
crash>
...

I was browsing the system from a Windows 10 NFS client workstation at
the time of the panic.

Chavdar


-- 
----
[prev in list] [next in list] [prev in thread] [next in thread]