As a first step, to diagnose problems with suspend, you will want to look at details in the
log-file /var/log/pm-suspend.log doen not exist, just run
sudo PM_DEBUG=true pm-suspend in a terminal window. NOTE: This will suspend your computer, so you're probably going to see the problem again, however, the
pm-suspend.log log-file should be there when you eventually re-start.
The file should contain a series of
[...] service [servicename] suspend suspend
statements (together with hook status messages & other useful stuff), followed by a series of
[...] service [servicename] suspend resume success
However, somewhere along the way, one or more of these will probably return an error and at that point suspend is inhibited. You may see a series of suspend changes being rolled back. To locate the problem you'd normally just need to identify which service call is throwing the error.
In this case, the log file doesn't seem to have any service
[servicename] suspend resume statements, so as a next step, can you suspend the notebook again, and try to resume by pressing the power button. Give it a couple of minutes, and if it fails to re-start re-boot by holding the power button down for 5 seconds. When you re-start, open a terminal and
run dmesg | less. Please update the original question to include the output from
dmesg | less.
I'd also suggest verifying that your swap-partition is correctly set, and in particular that it is at least at big as your installed RAM. This is a handy FAQ on Swap.
UPDATE: The output from
dmesg | less
that you posted includes the line:
[ 1.197601] PM: Hibernation image not present or could not be loaded.
(line 574 in the file) Again, this suggests a problem with hibernation (suspend-to-disk), but if you're sure that your problem is actually with suspend (i.e. suspend-to-RAM) then that can't be it. I also can't see any reported problems with your Intel/NVIDIA graphics.