On Tue, Dec 18, 2001 at 10:55:27AM +0000, Josef Karthauser wrote: > On Mon, Dec 17, 2001 at 01:41:28PM -0800, Matthew Dillon wrote: > > If it is a vnode deadlock you have to find which process or > > processes it is deadlocking against. > > > > Do a ps -axl -M vmcore.X -N kernel.X on the kernel core, > > pick out all the processes blocked on inode or whatever, > > then from gdb go to each process (proc N) and do a backtrace > > (back). > > I've a similar problem with -current from recent (within the last week > or two). > > genius# ps -axl -M vmcore.15 -N kernel.15 > (attached file) > > The back traces for the processes locked in inode is also attached. > > Being green to debugging this kind of thing what should I do next?
Maybe it's the maxusers 0 code. I saw your recent commit to work around not using the new config. I've rebuilt my kernel from scratch, clean. If it happens again I'll let you know. Joe
msg30250/pgp00000.pgp
Description: PGP signature
