Subject: Re: Another serious bug in NetBSD-1.6.1
To: Brian Buhrow <buhrow@lothlorien.nfbcal.org>
From: David Laight <david@l8s.co.uk>
List: tech-kern
Date: 03/13/2003 11:20:57
> #1  0xc030cb4f in cpu_reboot ()
> #2  0xc028375e in panic ()

Should the locking be disabled after a panic in order to get the dump out?
After all not much else should be running...

> #3  0xc02752c1 in lockmgr ()
> #4  0xc02a5a78 in genfs_lock ()
> #5  0xc02a4b5a in VOP_LOCK ()
> #6  0xc02a431d in vn_lock ()
> #7  0xc029df7c in vget ()
> #8  0xc0245733 in ffs_sync ()
> #9  0xc02a0242 in sys_sync ()
> #10 0xc029f262 in vfs_shutdown ()
> #11 0xc030cb27 in cpu_reboot ()
> #12 0xc028375e in panic ()
> #13 0xc03134ce in trap ()
> #14 0xc0100bf7 in calltrap ()
> #15 0xc02a7021 in genfs_putpages ()

Any chance of working out whereabouts in genfs_putpages 0xc02a7021 is?

> #16 0xc0247471 in ffs_putpages ()
> #17 0xc02a4fc9 in VOP_PUTPAGES ()
> #18 0xc0247080 in ffs_full_fsync ()
> #19 0xc0246df0 in ffs_fsync ()
> #20 0xc02a481c in VOP_FSYNC ()
> #21 0xc0245767 in ffs_sync ()
> #22 0xc02a9b70 in sync_fsync ()
> #23 0xc02a481c in VOP_FSYNC ()
> #24 0xc02a98e9 in sched_sync ()


	David

-- 
David Laight: david@l8s.co.uk