mapbench with more than one thread seems to frequently hang on josmp and eventually cause a kernel panic..

You can enable by setting LOCKSTAT in param.h and use by running
lockstat (e.g. $ lockstat mapbench).

You must call destroylock before freeing the memory holding lockstat
enabled lock.  I did this for most of the locks.

I might have broken something, but gc threads were running too
infrequently for testing.  A gc thread might run at a higher rate due
to the heuristic in gc_end_epoch.