Configure just kdb on (I use about 15000 symbols).
Don't configure gdb.
Configure xfs, pagebuf, pagebuf locking, avl as modules.
make sure ctl A or break gets you the
kdb> prompt at the console.
Make sure you can type:
to kdb. try btp 1 to see init's stack.
Then, run the test and when things are hung, type ctl A or break
and do the above to see what the stacks are.
If you can't get kdb's prompt, ... we will need to figure something else
out like setting a break point at some common location that we hit
regularly like xfs_sync or ... but not too often.
When things appear hung, you can hopefully still get the breakpoint to
kick in when the clock goes off (assuming those aren't disabled, too).
>> > Just to make sure - you did set it up to run in your XFS partition didn't
>> > you
>> > It defaults to running in /usr/tmp which you probably do not have set up
>> > as X
>> Yes I did, I was very careful about that, looks like our configurations are a
>> little different, that could have something to do with it. Try turning off
>> pagebuf meta data.
>That fixed the problem.
>I am open to turning it back on again and helping to track down the problem if
>someone can give me a suggestion on how to go about it.