Joseph, feels kind'a silly for me to have you building kernels for me to test, so I went ahead and did the bisect myself to save you that time.
Making a quick summary of this behavior
Kernel <= 3.3 : System is able to successfully resume multiple times. Everything works.
3.4-RC1 : System reboots while trying to resume from *first* suspend
3.4-RC2 -> 3.8 (current): System recovers from first suspend, never recovers from second suspend.
6742259866d03d5bc19815441ba928e8378343dc is the first commit that exhibits the behavior described on this bug. This is a result of a merge between 2 branches.
- dba69d1092e291e257fb5673a3ad0e4c87878ebc: part of the 3.3 series, everything works great;
- 20d9d9a0544436b1b8c94689c01d746d6bd5525c : follows v3.4-rc1. System reboots while trying to resume from *first* suspend
Is there any other info I can provide? I can also try to see where between 3.3 and 3.4-RC1 it started to reboot
Joseph, feels kind'a silly for me to have you building kernels for me to test, so I went ahead and did the bisect myself to save you that time.
Making a quick summary of this behavior
Kernel <= 3.3 : System is able to successfully resume multiple times. Everything works.
3.4-RC1 : System reboots while trying to resume from *first* suspend
3.4-RC2 -> 3.8 (current): System recovers from first suspend, never recovers from second suspend.
6742259866d03d5 bc19815441ba928 e8378343dc is the first commit that exhibits the behavior described on this bug. This is a result of a merge between 2 branches.
- dba69d1092e291e 257fb5673a3ad0e 4c87878ebc: part of the 3.3 series, everything works great;
- 20d9d9a0544436b 1b8c94689c01d74 6d6bd5525c : follows v3.4-rc1. System reboots while trying to resume from *first* suspend
Is there any other info I can provide? I can also try to see where between 3.3 and 3.4-RC1 it started to reboot