again, i am not so sure that we're rare unfortunate cases. have you seen this passage from a recent ars technica review?
QUOTE
Finally, we have to note that we experienced two kernel panics during our battery testing. In both cases, it appears as if the kernel panic was triggered by putting the machine into standby mode when the battery was close to running out. Both times the machine appeared unresponsive after opening, and the display wouldn't come on. Pressing the power button to boot the machine didn't work; instead, we had to hold down the power button to power the machine off first, and then power it back on (this is a case where some sort of independent battery indicator would have helped figure out what was happening).
We discussed the issue with Apple, and provided them with crash logs, though at press time the company was unable to determine the exact cause of the problem. To our knowledge, no other reviewers have noted similar issues, and Apple said that our report was the first to detail such a problem. However, Cult of Mac noted over the weekend that at least one staffer has experienced kernel panics with a new MacBook Air.
END QUOTE (source:
http://ke-we.net/8jc)
of course i have no statistics, but my gut feeling tells me there is something pervasive going on here. also, some people writing above AWARE OF THE PROBLEM returned their unit ONLY TO ENCOUNTER THE ISSUE AGAIN. in one case i've read about even three times in a row. this stinks!
it reminds me of the faint grey lines on previous generation macbook air displays. most people did not complain about them, did not even see them. but they were definitely there, you just had to be perfectionist enough. i examined many models and actually never saw one without them. would've bought it otherwise.
granted, the present issue is not something debatable (but then the lines weren't really either) because it's just and undeniably there. anyway, i am actually pretty optimistic that a solution will be found. (whereas with the lines, i was very skeptical; it seemed too much of a hardware issue to me. here, as i said, i think software or firmware updates will fix it.)