illumos gate

Kernel panic caused when automounting a stale nfs share from a remote machine. The share existed, but the directory did not. This is present in messages:

Inline Code
Jan 3 11:30:39 nas1 ^Mpanic[cpu0]/thread=ffffff07108d3440:
Jan 3 11:30:39 nas1 genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff002e838490 addr=108 occurred in module "unix" due to a NULL pointer dereference
Jan 3 11:30:39 nas1 unix: [ID 100000 kern.notice]
Jan 3 11:30:39 nas1 unix: [ID 839527 kern.notice] nfsd:
Jan 3 11:30:39 nas1 unix: [ID 753105 kern.notice] #pf Page fault
Jan 3 11:30:39 nas1 unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x108
Jan 3 11:30:39 nas1 unix: [ID 243837 kern.notice] pid=626, pc=0xfffffffffb86cdbb, sp=0xffffff002e838588, eflags=0x10246
Jan 3 11:30:39 nas1 unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 6f8<xmme,fxsr,pge,mce,pae,pse,de>
Jan 3 11:30:39 nas1 unix: [ID 624947 kern.notice] cr2: 108
Jan 3 11:30:39 nas1 unix: [ID 625075 kern.notice] cr3: 63fc75000
Jan 3 11:30:39 nas1 unix: [ID 625715 kern.notice] cr8: 0
Jan 3 11:30:39 nas1 unix: [ID 100000 kern.notice]
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] rdi: 108 rsi: ffffff0818b6de38 rdx: ffffff07108d3440
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] rcx: ffffff002e8387d0 r8: 0 r9: ffffff06fee4c0cc
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] rax: 0 rbx: ffffff002e8388c0 rbp: ffffff002e8385b0
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] r10: 511a000000000003 r11: ffffff093ba18688 r12: 108
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] r13: 0 r14: ffffff002e838b00 r15: 0
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] fsb: 0 gsb: fffffffffbc30520 ds: 4b
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] es: 4b fs: 0 gs: 1c3
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] trp: e err: 2 rip: fffffffffb86cdbb
Jan 3 11:30:39 nas1 unix: [ID 592667 kern.notice] cs: 30 rfl: 10246 rsp: ffffff002e838588
Jan 3 11:30:39 nas1 unix: [ID 266532 kern.notice] ss: 38
Jan 3 11:30:39 nas1 unix: [ID 100000 kern.notice]
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838360 unix:die+dd ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838480 unix:trap+17db ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838490 unix:cmntrap+e6 ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e8385b0 unix:mutex_enter+b ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838770 nfssrv:rfs3_lookup+5fc ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838a70 nfssrv:common_dispatch+384 ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838a90 nfssrv:rfs_dispatch+2d ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838b70 rpcmod:svc_getreq+19c ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838bd0 rpcmod:svc_run+171 ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838c00 rpcmod:svc_do_run+81 ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838ec0 nfs:nfssys+765 ()
Jan 3 11:30:39 nas1 genunix: [ID 655072 kern.notice] ffffff002e838f10 unix:brand_sys_sysenter+1c9 ()
Inline Code

This very well could be the same as Bug #3449, but in our case, the circumstances are known and reproducible.