Just another point to consider, looking at the S3 magic number debug:
[ 1.181366] registered taskstats version 1 [ 1.182071] Magic number: 0:523:740 [ 1.182151] hash matches /build/buildd/linux-2.6.32/drivers/base/power/main.c:471
This corresponds to the device_resume() function terminating correctly with a error value of 0 (which means it worked successfully) - so it appears that all the drivers have been resumed correctly in this function.
Just another point to consider, looking at the S3 magic number debug:
[ 1.181366] registered taskstats version 1 buildd/ linux-2. 6.32/drivers/ base/power/ main.c: 471
[ 1.182071] Magic number: 0:523:740
[ 1.182151] hash matches /build/
This corresponds to the device_resume() function terminating correctly with a error value of 0 (which means it worked successfully) - so it appears that all the drivers have been resumed correctly in this function.