-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
| I think the patch where I essentially did a printk if I hit it a second | time crashes. So I'm pretty sure suspend is getting suspended twice as I | did indeed crash :) I also did a big printk in there as the first move and it neither crashes nor printed twice here with a defconfig-2.6.24 kernel. But I don't doubt what you're telling me one bit. However I did a bunch of work on this today which is on andy branch now, together with "really fast resume", ~450ms to userspace running. It includes the same logic or pcf50633 resume you proposed about seeing if we are already suspended and confirms it is in the SUSPEND state on the pm_message_t state argument. One of the things added was some tracebacks that will fire if anything tries to read or write to PMU register while PMU considers itself still suspended. I found and fixed a bad guy (glamo mmc) that way and it'll be interesting to hear about any stack traces you get with your different config. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkhQIPwACgkQOjLpvpq7dMphJgCfROpeTQsfFz5aqGGv3wbKWoHc xjkAn2nkrBWBHjLAP7wuXW8xfGV+QEG5 =EepD -----END PGP SIGNATURE-----
