Hi! A couple hours later, my shell was in an NFS mounted directory (probably idle for some time) and I tried tab-completing an entry, and it panicked again. Same location as below.
Hand copied: tcp_shutdown_wrapper+0x20 nfs_disconnect+0x69 nfs_reconnect+0x1a nfs_request+0x7fb nfs_access+0x1ed VOP_ACCESS+0x61 nfs_lookup+052f VOP_LOOKUP+0x8a lookup_once+0x1a6 namei_tryemulroot+0xb00 namei+0x29 vn_open+0x133 do_open+0xc3 do_sys_openat+0x74 sys_open+0x24 syscall+0x196 Thomas > On 29.10.2022, at 11:53, Thomas Klausner <w...@netbsd.org> wrote: > > Hi! > > I’ve upgraded from 9.99.100 (stable) to 9.99.104 this morning (kernel + user > land, but packages still the old ones built on 9.99.100 in case it matters). > A couple hours later I started transmission-gtk and the machine immediately > panicked. > > Hand copied: > > uvm_fault(0xfffff8b04ab6d8f0, 0x0, 1) -> e > Fatal page fault in supervisor mode > Trap type 6 code 0 rip 0xffffffff80b06b82 cs 0x8 rflags 0x10246 cr2 0x38 > ilevel 0 rsp 0xfffffc62191caaaf0 > Curlwp 0xffffff8b08ac6d040 pid 6904.22757 lowest kstack 0xfffffc62191ca62c0 > Kernel: page fault trap, code = 0 > Stopped in pid 6904.22757 (transmission-gtk) at > netbsd:tcp_shutdown_wrapper+0x20 > : movq 38(%rax), %r14 > tcp_shutdown_wrapper() at netbsd:tcp_shutdown_wrapper:0x20 > nfs_disconnect() at netbsd:nfs_disconnect+0x69 > nfs_reconnect() at netbsd:nfs_reconnect+0x1a > nfs_request() at netbsd:nfs_request+0x7fb > nfs_statvfs() at netbsd:nfs_statvfs+0x173 > VFS_STATVFS() at netbsd:VFS_STATVFS+0x22 > dostatvfs() at netbsd:dostatvfs+0x132 > do_sys_getvfsstat() at netbsd:do_sys_getvfsstat+0x9f > sys___getvfsstat90() at netbsd:sys___getvfsstat90+0x2b > syscall() at netbsd:syscall+0x196 > > I have nfs mounted some shares from a Synology station. > > Ideas? Perhaps the pcb merge changes from this week? > Thomas