Comment 4 for bug 1006215

About the above failures, the confirmation result as following:

Build ID: 309
LAVA Job ID: 20819
Board Used: Snowball03
Problems:
1. When running the CTS test, the android hanged up.
2. When running monkey test under the hanged up state, the reboot will failed because there is no "Hit any key to stop autoboot" displayed.

Build ID: 310
LAVA Job ID: 20896
Board Used: Snowball03
Problems:
1. When running the glmark2 test, the android hanged up
2. When running next test under the hanged up state, the reboot will failed because there is no "Hit any key to stop autoboot" displayed.

Build ID: 316
LAVA Job ID: 21339
Board Used: Snowball01
Problems:
1. When running the CTS test, the android hanged up

Build ID: 318
LAVA Job ID: 21339
Board Used: Snowball01
Problems:
1. When running the mmtest test, the android crashed
2. When running the CTS test, the android hanged up.
3. When running monkey test under the hanged up state, the reboot will failed because there is no "Hit any key to stop autoboot" displayed.

So the mainly problems should be:
1. The android will hang up when running some test, especially when run CTS.
    But not know if it is the CTS test make it hang up.
2. Then reboot under hang up state will failed in most cases. Because there is no "Hit any key to stop autoboot" displayed when hard reset