Comment 42 for bug 990575

I managed to reproduce the bad suspend behaviour (on 3.2.0.23) with an overnight run. Run failed to properly suspend and resume after only 12 times.

Kernel message output was display on screen at time of failure, mouse + keyboard were unresponsive:
kernel: [ 88.556310] watchdog: only one watchdog can use /dev/watchdog.
kernel: [ 88.556316] watchdog: error registering /dev/watchdog (err=-16).

Suspend failure:

00012 s3 S3 suspend/resume test.
00013 s3 -----------------------------------------------------------------------------
00014 s3 Test 1 of 1: S3 suspend/resume test.
00015 s3 S3 cycle 1 of 100
00016 s3 pm-suspend returned 0 after 38 seconds.
00017 s3 S3 cycle 2 of 100
00018 s3 pm-suspend returned 0 after 37 seconds.
00019 s3 S3 cycle 3 of 100
00020 s3 pm-suspend returned 0 after 37 seconds.
00021 s3 S3 cycle 4 of 100
00022 s3 pm-suspend returned 0 after 38 seconds.
00023 s3 S3 cycle 5 of 100
00024 s3 pm-suspend returned 0 after 37 seconds.
00025 s3 S3 cycle 6 of 100
00026 s3 pm-suspend returned 0 after 37 seconds.
00027 s3 S3 cycle 7 of 100
00028 s3 pm-suspend returned 0 after 37 seconds.
00029 s3 S3 cycle 8 of 100
00030 s3 pm-suspend returned 0 after 38 seconds.
00031 s3 S3 cycle 9 of 100
00032 s3 pm-suspend returned 0 after 38 seconds.
00033 s3 S3 cycle 10 of 100
00034 s3 pm-suspend returned 0 after 37 seconds.
00035 s3 S3 cycle 11 of 100
00036 s3 pm-suspend returned 0 after 37 seconds.
00037 s3 S3 cycle 12 of 100