More about system lockup under heavy load.
~# ... DDB break in works ... db> bt 0x0060bd90: at comintr+0x590 0x0060bde0: at pic_handle_intr+0x198 0x0060be20: at trapstart+0x684 0x0060bef0: at sched_curcpu_runnable_p+0x2c <<< THIS <<< 0x0060bf00: at idle_loop+0xe8 0x0060bf20: at setfunc_trampoline+0x8 saved LR(0x7ffffd) is invalid. ... The last operation I did is invoking "ps xa" and DDB shows no ps process.
It's now quite obvious it's the "schedular stuck" The DDB traceback is the same as GCC4.5 genautomata lockup case. db> bt 0x0060bd90: at comintr+0x590 0x0060bde0: at pic_handle_intr+0x198 0x0060be20: at trapstart+0x684 0x0060bef0: at sched_curcpu_runnable_p+0x2c <<< HERE <<< 0x0060bf00: at idle_loop+0xe8 0x0060bf20: at cpu_lwp_bootstrap+0xc saved LR(0x7ffffd) is invalid. Toru Nishimura / ALKYL Technology