My comment was aimed at all the people that have never had the issue occur naturally yet are trying to make it happen.
Well, in some senses, this is important. For me, the problem occurred simply as part of the normal transfer of data from my old machine to the new one. An occasional "glitch" is expected, particularly with new product. But after four hangs in several hours, each requiring a hard reset, one begins to wonder if there's a problem. That's what led to the various diagnostic tests to see if the problem could be reliably demonstrated.
I'd LOVE for the vast majority to be saying, "There's no problem at all -- these are isolated cases." That would give me confidence that I simply got a bad machine. But when I read about people getting two and three replacements from different locations, and still being able to reproduce the freezes, it begins to look much more like a systemic problem. Remember, we're not talking at all about over-taxing machines here... true, the dev/null test and the major compilation tests DO tax the machines, but the vast majority of freezes I (and others) have experienced happened randomly, when the machine was essentially sitting idle -- no exceptional heat, no out-of-the-ordinary activities -- just switching between windows, running a screen saver, waking from sleep, or just sitting around with the 8 threads contemplating a restful snooze on the beach (ok, so it's a silicon beach!)
Apart from a few people who HAVE chimed in and said "I don't have a problem", many, many others have been able to reproduce the issue when they've tried one or other of the methods to recreate the issue. So, maybe it's truly the case that there are a few, isolated issues, and these are the ones getting the press -- but every day we see more and more people highlighting this, thinking that "they were the only one seeing this"...
For me, this isn't an academic question. I cannot trust a machine that is going to die randomly during my work day. I know from personal experience that this will end up corrupting a disk, losing valuable data or wasting a whole lot of time for people counting on the results of what I do. I've had Macs for almost 20 years and apart from failures which ultimately could fully be explained as either hardware failure (and then replacement parts have solved the issue) or software problems (which have gone away when the offending software has been removed), I've never seen an out-of-the-box/vanilla-installation-of-Mac-OS-anything fail with such regularity as this new machine...
So, thanks to all who are helping to identify whether a bunch of us simply have a "bad lot" (in which case replacements under warranty will fix everything just fine), or whether there really is a systemic issue that suggests it will be better to wait until "Rev. B"...
Cheers,
S