Please follow this document to do some basic debugging on an upstream kernel.
https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt

I'm sorry I didn't reply sooner.
I've followed the document and done the following debugging:

# echo reboot > /sys/power/disk
# echo disk > /sys/power/state

# echo platform > /sys/power/disk
# echo disk > /sys/power/state

# echo shutdown > /sys/power/disk
# echo disk > /sys/power/state

and this but I'm not sure if this is what I should have done because I'm confused with how I should do the 5 test modes.:

# echo devices > /sys/power/pm_test
# echo platform > /sys/power/disk
# echo disk > /sys/power/state

ALl of the above failed to hibernate computer.To test the remaining options I need to know better how I should use the test modes.
I understand by looking at the first 3 modes that # echo disk > /sys/power/state issues the standard hibernation commands.However this is what is confusing:

to use the "devices" test mode along with the "platform" mode of hibernation,
you should do the following:

# echo devices > /sys/power/pm_test
# echo platform > /sys/power/disk

Why doesn't platform need to be written to /sys/power/pm_test but to /sys/power/disk as if I to hibernate the computer using the platform mode not actually testing the platform mode and why use devices along with platform? (Description of "platform" explains that "platform" is the same as "devices" but it also uses platform global control methods)

I wish I could edit or delete my previous post.This is what I should have written:

> I'm sorry I didn't reply sooner.
> I've followed the document and done the following debugging:
> 
> # echo reboot > /sys/power/disk
> # echo disk > /sys/power/state
> 
> # echo platform > /sys/power/disk
> # echo disk > /sys/power/state
> 
> # echo shutdown > /sys/power/disk
> # echo disk > /sys/power/state
> 
> # echo devices > /sys/power/pm_test
> # echo platform > /sys/power/disk
> # echo disk > /sys/power/state
> 
> All of the above failed to hibernate computer.I will test the remaining
> tests starting from freezer and I will do each test 3 "times in a row for    
>  > confidence" (is this enough?)
> Should I test each test mode along with each standard mode?

When you are testing device mode, no need to change test mode.

# cd /sys/power
# echo freezer > pm_test
# echo disk > state

Does this fail? If so, what's the error messages?
If not, continue to the next level:
# echo devices > pm_test
# echo disk > state
and go on till core. Let me know the result first, thanks.

I tested freezer 3 times yesterday and 3 times again just now.The first time today the PC stopped responding and started responding again after screen goes black for a splitsecond.The following tests show the same messages: http://picpaste.com/IMG_20140326_231748-36VJtdtK.jpg and go back to the desktop.

However echo devices > pm_test always gets stuck at a blank black screen for at least several minutes (leaving the computer unresponding, doesn't respond to caps lock etc keys) so I don't see any error messages.

I'm assuming you mean "When you are testing device mode, no need to change platform mode."

I shall continue debugging by finding the offending module/s tomorrow.

(In reply to mubtcez from comment #5)
> I tested freezer 3 times yesterday and 3 times again just now.The first time
> today the PC stopped responding and started responding again after screen
> goes black for a splitsecond.The following tests show the same messages:
> http://picpaste.com/IMG_20140326_231748-36VJtdtK.jpg and go back to the
> desktop.
> 
> However echo devices > pm_test always gets stuck at a blank black screen for
> at least several minutes (leaving the computer unresponding, doesn't respond
> to caps lock etc keys) so I don't see any error messages.

This sounds like a device driver issue.

> 
> I'm assuming you mean "When you are testing device mode, no need to change
> platform mode."
> 
> I shall continue debugging by finding the offending module/s tomorrow.

Yes, find out the driver module that blocks the suspend.

mubtcez@yandex.com, any update?

@Zhang Rui I'm sorry I couldn't help to solve this issue lately, I should continue debuging soon.

Unfortunately hardware issues are delaying my progress again.I'm sorry for the inconvienience.

That's okay. I will close this bug later if you can not do any debugging for a month.
But please feel free to re-open it when you're able to debug. Does this sound okay to you?

zhang@intel.com
aaron.lu@intel.com

I updated the kernel image and headers to 3.16-rc3 should I change

(In reply to mubtcez from comment #11) I'm sorry for accidental sending. (I don't have any edit option)
> zhang@intel.com
> aaron.lu@intel.com
> 
I'm not sure if all of this information is useful.

I updated the kernel image and headers to 3.16-rc3 by installing .deb files from kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc3-utopic .I didn't apply the patches. 
So I changed the Kernel Version is this OK?

I first tried hibernating in "reboot" and "platform" and "shutdown" modes.
The reboot mode sometimes causes the computer to freeze or rarely to reboot at the time when the OS normally starts to boot.On the earlier version I experienced the whole screen being red with some 'glitter' on the upper middle part with this mode.The two other modes caused only freezes.

After that I've tested the hibernation test modes incrementally but only with 
echo shutdown > /sys/power/disk.
I have only noticed issues when testing echo core > /sys/power/pm_test.

The issues I've noticed are:
Computer seems unresponsive (at least when resuming finishes and maybe after)
Sometimes videos won't play anymore (on YouTube, I can change from what part to play but it only shows the same frame and a buffering animation)
Sometimes I get disconnected from network 
(dmesg says [ 6070.599541] r8169 0000:00:0b.0 eth0: link down)

Using this command I've obtained dmesg logs right before and after using  
echo core > /sys/power/pm_test:

dmesg > dmesg_before; echo disk > /sys/power/state; dmesg > dmesg_after

The logs are here: http://pastebin.com/DbwE72ZF http://pastebin.com/6DDZuh92

Created attachment 141951 [details]
For comment 12        dmesg_before

Created attachment 141961 [details]
For comment 12        dmesg_after

(In reply to mubtcez from comment #12)
> After that I've tested the hibernation test modes incrementally but only
> with 
> echo shutdown > /sys/power/disk.
> I have only noticed issues when testing echo core > /sys/power/pm_test.
> 
> The issues I've noticed are:
> Computer seems unresponsive (at least when resuming finishes and maybe after)
> Sometimes videos won't play anymore (on YouTube, I can change from what part
> to play but it only shows the same frame and a buffering animation)

What if you refresh the page?

> Sometimes I get disconnected from network 
> (dmesg says [ 6070.599541] r8169 0000:00:0b.0 eth0: link down)

Does it keep the link down state forever or it will became up a moment later?

**This is intended for all my posts here: I know that some things might not be relevant but when I'm in doubt I write it out**
BIOS POST screen shows that CPU stepping is CG.

> No matter what youtube page I view this still happens.
>
> It keeps the link down state forever.

I also don't have my sound card connected anymore as it just stopped working.(It worked until a reboot, don't know why) and usb something I don't know the proper name of (same as picture but has another cable with yellow ending http://i.stack.imgur.com/lJU49.jpg ) and new ps/2 keyboard (usb keyboards fail with error 110, details here: http://unix.stackexchange.com/questions/147723/usb-3-2-cant-set-config-1-error-110-usb-keyboard-works-in-windows-8-lap )



I've just tested shutdown mode with processors mode twenty four times and no problems except that bash doesn't respond to keypresses randomly and all is "laggy" for a few minutes after.

Maybe this bash issue isn't caused by the testing of hibernation but my script.

echo shutdown > /sys/power/disk && echo processors > /sys/power/pm_test
while :; echo testing shutdown mode with processors mode; do sleep 5; dmesg > dmesg_before; echo disk > /sys/power/state; dmesg > dmesg_after; sleep 15; done

I've tested the same thing but with core mode instead of processors mode eighteen times.Nothing on screen responded except mouse moving.The keyboard responded normally.The background was black (I guess it didn't load) I waited for PC to respond again and I found out that it returned to login screen as always after 10 minutes of inactivity and it worked normally until I've logged on.After unlocking PC the exact same thing was happening.That's when I switched to terminal (using ctrl alt f1) I (entered restart lightdm) to start a new desktop session.

Immediately after desktop loaded I saw a notification saying ethernet is disconnected as in previous tests.(the processors mode doesn't disconnect) I also couldn't get the power menu to show (reboot command worked though)

Created attachment 145241 [details]
For #16 - before

Created attachment 145251 [details]
For #16 after

Hi,
I saw the log with "PM: Image restored successfully."
and it seems a successful resuming from hibernation, 
I don't know what the problem is now?
thanks

I notice this bug is one year ago.. and the hibernation code has changed a lot, can you please help to confirm if the problem still exist on latest kernel ?
And I also checked your comment at #Comment 16, I think the graphic driver has also changed a lot during the past year, so it's better to confirm at kernel 4.3, and I can do more debugging with your latest result.
Thanks.
Yu

ping..