Re: kern/46221: Kernel panic in NFS server code

[Matthias Scheler <tron%zhadum.org.uk@localhost>]

The following reply was made to PR kern/46221; it has been noted by GNATS.

From: Matthias Scheler <tron%zhadum.org.uk@localhost>
To: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
Cc: NetBSD GNATS <gnats-bugs%NetBSD.org@localhost>
Subject: Re: kern/46221: Kernel panic in NFS server code
Date: Sun, 18 Mar 2012 17:44:41 +0000

 On Sun, Mar 18, 2012 at 04:10:08PM +0000, Manuel Bouyer wrote:
 >  On Sun, Mar 18, 2012 at 03:55:00PM +0000, tron%zhadum.org.uk@localhost 
 > wrote:
 >  > >Number:         46221
 >  > >Category:       kern
 >  > >Synopsis:       Kernel panic in NFS server code
 >  > >Confidential:   no
 >  > >Severity:       serious
 >  > >Priority:       high
 >  > >Responsible:    kern-bug-people
 >  > >State:          open
 >  > >Class:          sw-bug
 >  > >Submitter-Id:   net
 >  > >Arrival-Date:   Sun Mar 18 15:55:00 +0000 2012
 >  > >Originator:     Matthias Scheler
 >  > >Release:        NetBSD 6.0_BETA 2012-03-16 sources with fix for PR 
 > kern/45677
 >  > >Organization:
 >  > Matthias Scheler                                  http://zhadum.org.uk/
 >  > >Environment:
 >  > System: NetBSD colwyn.zhadum.org.uk 6.0_BETA NetBSD 6.0_BETA (COLWYN.64) 
 > #0: Fri Mar 16 13:40:20 GMT 2012 
 > tron%colwyn.zhadum.org.uk@localhost:/src/sys/compile/COLWYN.64 amd64
 >  > Architecture: x86_64
 >  > Machine: amd64
 >  > >Description:
 >  > My NetBSD/amd646 6.0_BETA server has crashed three times during access by
 >  > a Mac OS X NFS client. It rebooted twice. But in one case it got stuck
 >  > and I could copy this traceback from the console:
 >  > 
 >  > printf_nolog() at netbsd:printf_nolog
 >  > wddump() at netbsd:wddump+0x23d
 >  > raiiddump() at netbsd:raiddump+0x227
 >  > dumpsys_seg() at netbsd:dumpsys_seg+0xb9
 >  > dump_seg_iter() at netbsd:dump_seg_iter+0xfb
 >  > dodumpsys() at netbsd:dodumpsys+0x273
 >  > dumpsys() at netbsd:dumpsys+0x1d
 >  > vpanic() at netbsd:vpanic+0x1dd
 >  > printf_nolog() at netbsd:printf_nolog
 >  > startlwp() at netbsd:startlwp
 >  > alltraps() at netbsd:alltraps+0xa2
 >  > ffs_fhtovp() at netbsd:ffs_fhtovp+0x55
 >  > VFS_FHTOVP() at netbsd:UFS_FHTOUP+0x1c
 >  > nfsrv_fhtovp() at netbsd:nfsrv_fhtovp+0x9a
 >  
 >  Could you build a kernel with makeoptions    DEBUG="-g", reboot it
 >  and try to reproduce the problem ?
 
 I always built kernel with that option.
 
 > It would be interesting to see where ffs_fhtovp+0x55 points to in sources.
 
 If you pleae tell me how to find that out in gdb(?) I will happily provide
 the information. Alternatively you can find the kernel image here:
 
        http://files.zhadum.org.uk/netbsd.gdb.xz
 
 > Also, if you don't get a crash dump, please set ddb.onpanic=1 so that
 > we get the kernel panic message, the instruction that faulted, and you can
 > dump registers content (it looks like it's a trap, so 'sh registers' will
 > print something interesting).
 
 I've already done that. I only forgot to do it again after Friday's
 kernel update and before the last crash.
 
        Kind regards
 
 -- 
 Matthias Scheler                                  http://zhadum.org.uk/