On Wed, Oct 10, 2007 at 10:26:49PM +0200, Kurt Schreiner wrote:

> Not yet, I'll do that tomorrow (at work) and post the "results". The hang can
> be reproduced very easy by just doing "build.sh -j 8 ..." (tried this afternoon
> -after userland was build.sh'ed -j8 running a kernel with the old scheduler w/o
> problems- output of bt was the same, but I've had no time to investigate further).

If it happens again, can you switch onto the other CPU (eg 'mach cpu 1') and
get a backtrace there? It looks like the two CPUs are deadlocked.

Andrew