Comment 9 for bug 191613

Please do not include kern.log. Instead, try a suspend/resume cycle and send the output of dmesg, since it is much more useful. In your kern.log, I see no remnants of a suspend attempt (note that your two files before and after attempt are empty. So in this case, the kernel has performed no actions, unless you just mistakenly attached the wrong file.