Comment 8 for bug 759213

I don't see a suspend in the dmesg you attached. So the machine was really rebooted after suspend, not resumed?

Hrm, I looked at CurrentDmesg.txt again and what's actually in there is a failed suspend, not a successful suspend/resume. So is the system locked hard when you try to resume it, or is it still responsive (i.e. you can still log into the system over ssh)? If you can get in via ssh, please use this to capture dmesg after resume, before rebooting.

If it's completely unresponsive after resume, try the pm_trace steps from https://wiki.ubuntu.com/DebuggingKernelSuspend. If that doesn't work there's something new we can try, it just takes a little bit of effort to get set up.