Dear Andrew, On 2020-04-08, Yorick Hardy wrote: > Dear Andrew, > > On 2020-04-07, Yorick Hardy wrote: > > Dear Andrew, > > > > On 2020-04-07, Andrew Doran wrote: > > > Hi Yorick. > > > > > > On Mon, Apr 06, 2020 at 11:16:37PM +0200, Yorick Hardy wrote: > > > > > > > Crash version 9.99.54, image version 9.99.54. > > > > crash: _kvm_kvatop(0) > > > > Kernel compiled without options LOCKDEBUG. > > > > System panicked: vrelel: bad ref count > > > > Backtrace from time of crash is available. > > > > crash> bt > > > > _KERNEL_OPT_NAGR() at 0 > > > > ?() at 7f7ff7ecf000 > > > > sys_reboot() at sys_reboot > > > > vpanic() at vpanic+0x181 > > > > vtryrele() at vtryrele > > > > vcache_dealloc() at vcache_dealloc > > > > uvm_unmap_detach() at uvm_unmap_detach+0x76 > > > > uvm_unmap1() at uvm_unmap1+0x4e > > > > uvm_mremap() at uvm_mremap+0x36b > > > > sys_mremap() at sys_mremap+0x68 > > > > syscall() at syscall+0x227 > > > > --- syscall (number 411) --- > > > > 7f0af7842e9a: > > > > > > Were you running anything noteworthy at the time? There is a very good > > > chance that is fixed by revision 1.217 of src/sys/kern/vfs_lookup.c. > > > > > > Thanks, > > > Andrew > > > > Thanks! It happens often when running wip/urlwatch, which keeps > > the disk quite busy. I will try a new kernel as soon as I can free > > up my computer! > > Initial tests are unable to trigger the panic, so it looks promising! > Let's assume it is fixed, I will continue to use this kernel and report > back if necessary. > > Thanks again!
I just had the same panic with 9.99.55: Crash version 9.99.55, image version 9.99.55. crash: _kvm_kvatop(0) Kernel compiled without options LOCKDEBUG. System panicked: vrelel: bad ref count Backtrace from time of crash is available. crash> bt _KERNEL_OPT_NAGR() at 0 ?() at 7f7ff7ecf000 sys_reboot() at sys_reboot vpanic() at vpanic+0x181 vtryrele() at vtryrele vcache_dealloc() at vcache_dealloc uvm_unmap_detach() at uvm_unmap_detach+0x76 uvm_unmap1() at uvm_unmap1+0x4e uvm_mremap() at uvm_mremap+0x36b sys_mremap() at sys_mremap+0x68 syscall() at syscall+0x227 --- syscall (number 411) --- 797459842e9a: crash> but I am not sure what caused it. I will update and try again. -- Kind regards, Yorick Hardy