MBA fails to wake (Platform Failure) after entering Low Power Sleep state

Question

2011 MacBook Air 13” model number A1369
The issue: every time the battery drains empty and the device automatically shuts off, it will not properly power-on after being charged.  The display backlight is active (and apple logo on the rear is illuminated) although the screen is blank.  The machine doesn’t respond to any command or action.  The machine will not respond to ping requests and does not appear to attempt to join the network according to the Airport logs.  Closing the clamshell and re-openning does not appear to make any difference.  The only action that yields any response is to hold the power button until it turns off and then turn it back on again.  This has happened 100% of the time since the MacBook Air was purchased. This behavior does not happen with the 2009 MacBook pro also running OSX Lion. 
pmset -g output:
Active Profiles:
Battery Power           -1*
AC Power                -1
Currently in use:
standbydelay   4200
standby        1
halfdim        1
panicrestart   15
hibernatefile  /var/vm/sleepimage
disksleep      10
sleep          10
hibernatemode  3
ttyskeepawake  1
displaysleep   5
acwake         0
lidwake        1
pmset -g log output of problem situation:
* Domain: sleep
- Message: Sleep: Success - BATT 0 - Low Power Sleep
- Time: 8/13/11 10:32:55 PM EDT
- Signature: Success
- UUID: 79B0FD75-93BF-4F54-9206-F88EFDD9539A
- Result: Success
- Sleep count : 0
* Domain: sleep
- Message: Sleep: Platform Failure - AC 82
- Time: 8/13/11 11:58:45 PM EDT
- Signature: Platform Failure
- UUID: 399B3402-C3A6-451B-B5AC-60CF6CD5176F
- Result: Failure
Observations:
FileVault is enabled
This issue does not seem to occur when the device enters the ‘hibernation’ state after sleeping for an extended-period of time
Actions taken (with no resolution yet):
SMC reset (multiple times)
PRAM reset
Set main HD (“Macintosh HD”) as Startup Disk
Complete reinstall of OSX Lion
Any advice?

Answer 1

I have the exact same issue 100% reproducible BUT I also know how to exercise the bug without needing to run down the battery.  Simply do sudo pmset -a destroyfvkeyonstandby 1 hibernatemode 25 then remove the power cord, close the clamshell, plug the power cord back in so it charges for a second, then open the clamshell.  You will be in the same blank screen state as if you had let the battery run out. 
hibernatemode 25 basically just tells the computer to go into hibernate mode instead of sleep mode wheenver you close the laptop. 
destroyfvkeyonstandby tells the computer to power down the ram as soon as it enter hibernate mode.
This problem is way worse than any of you suspect.  In all probability the system was intentionally broken in order to provide a backdoor into FV2.  Let me explain:
It's impossible to achieve a secure FV2 system without using the following settings:
sudo pmset -a destroyfvkeyonstandby 1 hibernatemode 25
because otherwise what will happen is your FV key will be stored in RAM during both sleep and hibernate states.  That means if a bad guy steals your laptop while it's in sleep or hibernate state he's then free to take an unlimited amount of time to attack it.  He will be able to retrieve the key from ram as DEMONSTRATED LIVE a few months ago at a security confrence.  The tools to preform the attack to retreive the key along with a detailed writeup are availble here:
http://www.frameloss.org/2011/09/18/firewire-attacks-against-mac-os-lion-filevau lt-2-encryption/
So at the risk of repeating myself... the conclusion is it's impossible to have a secure FV2 MBA system because of this bug.  I suspect it's a conspiracy because it's too convenient of a bug..
apple has the fV2 system insecure by default (key stored in ram by default) and then apple happens to have a bug that prevents you from flushing that key then hibernating which would be the secure way to do it. Too much of a coincidence.