First post here with half a clue and then you leave us in suspenders?
So, what did "
top" say?
Try running it with a short interval time and no sleep time, e.g. "
top -i 1 -o cpu -s 0".
Of course, that will make "
top" eat up all the CPU so maybe that's not such a good idea
I've seen serious (multiple second) "soft freezes" on my wheezing old Early 2006 MacBook Pro (2.16 GHz Core Duo model with 2 GB) when it is creating new swap files in "
/var/vm" from too much machine/memory loading.
I wonder if new swap files are being created in this case? Do all the machines affected have 8 GB of RAM?
P.S. This is what you get for being an Apple early adopter
Always wait for the 2nd or 3rd generation!
Sorry -- no intention to leave anyone in suspenders (sic).
The point was to say that the system froze almost immediately. At that point the whole screen updating stopped and the system was interactively non-responsive, but I could still SSH into it from another machine. Up until the machine froze (all of about 30 seconds), top showed what I expected -- 5 processes each consuming 100% of the CPU, PhotoBooth consuming about 30% and all the usual other stuff.
From research and reading all the posts (500+ now) in the main Apple Discussion thread on this it appears that:
1) Many people are able to create a hang / freeze with no additional software installed -- just a plain, new installation; also, the freezes seem to happen at random times -- from completely idle to waking from sleep, to running all cores at maximum load; sometimes software has been suspected (smcFanControl, etc.), but this is unfounded -- in many cases it is happening on a plain, vanilla, freshly installed system;
2) Many cite some improvement by forcing the machine to use either the discrete GPU or the internal GPU (conflicting! or at least pointing to a problem with the automatic switching) -- again, assertions that "this fixes the problem" are unfounded -- counter examples abound!
3) There are "freezes" that are "soft" -- in that the machine continues to run processes (iTunes, allowing SSH, etc.), although sometimes only until the end of a song (but sometimes beyond, so again, conflicting!); also, there are reports of "harder" freezes where everything stops functioning, or at least rapidly cascades to where everything stops;
4) There are those who report no problems -- some initially, and then after trying some of the tests, they discover that the machine does hang; -- others claim their machine seems to be impervious to hanging. This is both good news and bad news -- it points more to a bad batch of hardware than a driver issue (since the driver issue should affect ALL machines), but it does offer some hope that it is possible to get a "good" one;
5) As far as I can tell, this affects all new 2011 MacBook Pro Quad-Core 15" and 17" machines (with the apparent exception of those who are currently claiming imperviousness), regardless of disk type, disk size or amount of memory installed;
6) Interestingly, a 13" i7 user reported a problem, but this is the only instance I've seen of this.
I have a new machine coming to replace the faulty one (as soon as a courier calls to pick this one up) and I will thoroughly test it before installing ANYTHING else on it. Last time I was two full days into almost 500 GB of data migration when it started locking up randomly.
At this point, I'm not hopeful for an impervious one in round two, but I believe Apple will get it sorted. They have been professional, courteous, apologetic and very polite so far as, I like to think, have I, (although apologetic not so much...

).
Anyway, if anyone were looking for a recommendation to buy a new machine right now, my advice would be to wait for this to be resolved. This is the first time in FOREVER I have violated my inviolable principle of NEVER buying the first batch of anything Apple, and I have been properly rewarded for my impatience
Best of luck to all struggling with this issue...
Scott