During our testing, we have encountered an odd behavior when dealing with the AMT Remote Client. Using the Client Console, a remote terminal can be set into S3 mode, and then waken remotely. However, after this first cycle, the unit can no longer be placed in S3 or powered off remotely. When either command is generated, the unit will turn off briefly, and then turn back on. If a command to "Cycle Off/On Power" is sent, the unit will reboot. After the reboot, the unit can be placed in S3 one time, and will then continue behaving as described above. Is there an explanation for this behavior? (It appears that something is being set when the unit first goes into S3, but is not reset when the system recovers.)
For more complete information about compiler optimizations, see our Optimization Notice.