Re: NFS related panic? (was: Re: Killing a zombie process?)

On Fri 23 Oct 2015 at 00:46:57 +0200, Rhialto wrote: > This problem is very repeatable, usually within a few hours, just now it > happened within half an hour. > > It seems to me that somehow the nfs_reqq list gets corrupted. Then > either there is a crash when traversing it in nfs_timer()

Re: NFS related panic? (was: Re: Killing a zombie process?)

This problem is very repeatable, usually within a few hours, just now it happened within half an hour. It seems to me that somehow the nfs_reqq list gets corrupted. Then either there is a crash when traversing it in nfs_timer() (occurring in nfs_sigintr() due to being called with a bogus

Re: NFS related panic? (was: Re: Killing a zombie process?)

On Tue 20 Oct 2015 at 01:04:59 +0200, Rhialto wrote: > with a rebuilt netbsd.gdb (hopefully the addresses match) > > #5 0x806b94b4 in nfs_sigintr (nmp=0x0, rep=0xfe81163730a8, > l=0x0) at ../../../../nfs/nfs_socket.c:871 nmp should not be NULL here... let's look at rep, where it

Re: NFS related panic? (was: Re: Killing a zombie process?)

with a rebuilt netbsd.gdb (hopefully the addresses match) (gdb) target kvm netbsd.5.core 0x8063d735 in cpu_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at ../../../../arch/amd64/amd64/machdep.c:671 671 dumpsys(); (gdb) bt #0 0x8063d735 in

NFS related panic? (was: Re: Killing a zombie process?)

On Fri 16 Oct 2015 at 16:31:18 +0200, J. Hannken-Illjes wrote: > On 16 Oct 2015, at 13:44, Rhialto wrote: > > > "Interesting" results: it built packages overnight (from around 22:30 to > > 12:13, so for nearly 14 hours), then, when I didn't look, it rebooted. > > With panic? I