Help on diagnosing Torque lockup issues

I have recently developed an issue where my game is consistently locking up while loading a single player game on my Linux build. After initiating the load, I can no longer bring up the console or anything. I am having a very hard time figuring out what is going on. Whatever tools I use to diagnose the problem don't give me enough info (given my knowledge level of the Torque engine) or actually cause the problem to not appear. I've tried turning Trace on -- but that only gives me so much (see below). Running the game with the debug build under gdb makes it work. Running it with strace attached almost always makes it work. When it doesn't, it stops at the gettimeofday() syscall and just sits there.

When I turn on trace right after my car selection screen, it successfully calls GameConnection::loadMission() and echos ""*** Sending mission load to client: game/data/missions/NEW_TEST_6M.mis". But clientCmdMissionStartPhase1 is never called.

It must be some kind of timing issue because many of the things I am trying (debug build, syscall watching, etc) slow down the system.

Any suggestions on how to better track down what's going on? Or suggestions on what it might be?

Thanks!