On Thu, 21 Mar 2002, Nickolai Zeldovich wrote: > On Solaris, this is really easy: you find the struct proc for the > hung process, and look at the stack trace starting at tlist->sp. :) > Probably kgdb lets you do similar things on Linux. You might try > using cmdebug remotely, if the in-kernel Rx server is still working; > this sounds like a deadlock of some sort, which should show up in > cmdebug output in some way. You could also enable lock tracing, in > which case your fstrace output should tell you where the deadlock > occurred (assuming you can usefully run fstrace).
I never got lock tracing (via fstrace) to work on Linux, just fyi. I ended up using printks to do it instead. -D _______________________________________________ OpenAFS-devel mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-devel
