I started randomly hybridizing the working and failing .configs, and bisected the problem down to this difference:
--- bad4 2012-11-27 07:52:28.535253255 -0500
+++ good6 2012-11-27 07:35:58.376369630 -0500
@@ -3850,6 +3850 @@
-CONFIG_LOCKUP_DETECTOR=y
-CONFIG_HARDLOCKUP_DETECTOR=y
-# CONFIG_BOOTPARAM_HARDLOCKUP_PANIC is not set
-CONFIG_BOOTPARAM_HARDLOCKUP_PANIC_VALUE=0
-# CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC is not set
-CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=0
+# CONFIG_LOCKUP_DETECTOR is not set
That is, if I turn off CONFIG_LOCKUP_DETECTOR, suspend starts working again.
I started randomly hybridizing the working and failing .configs, and bisected the problem down to this difference:
--- bad4 2012-11-27 07:52:28.535253255 -0500 LOCKUP_ DETECTOR= y HARDLOCKUP_ DETECTOR= y BOOTPARAM_ HARDLOCKUP_ PANIC is not set BOOTPARAM_ HARDLOCKUP_ PANIC_VALUE= 0 BOOTPARAM_ SOFTLOCKUP_ PANIC is not set BOOTPARAM_ SOFTLOCKUP_ PANIC_VALUE= 0 LOCKUP_ DETECTOR is not set
+++ good6 2012-11-27 07:35:58.376369630 -0500
@@ -3850,6 +3850 @@
-CONFIG_
-CONFIG_
-# CONFIG_
-CONFIG_
-# CONFIG_
-CONFIG_
+# CONFIG_
That is, if I turn off CONFIG_ LOCKUP_ DETECTOR, suspend starts working again.