Bug 2386

Summary: [Crownbay]The system can resume from S3 standby mode automatically
Product: [Build System, Metadata & Runtime] BSPs Reporter: yilong, sun <yilongx.y.sun>
Component: bsps-configurationAssignee: Tom Zanussi <tom.zanussi>
Status: RESOLVED NOTABUG QA Contact:
Severity: minor    
Priority: Low CC: corneliux.stoicescu, dvhart, yp.bsp.watcher, yp.watcher
Version: 1.2   
Target Milestone: 1.3   
Hardware: x86   
OS: Multiple   
Whiteboard: (P3)(No QA needed)
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description yilong, sun 2012-05-02 03:12:59 UTC 
Testing environment:    
Hardware: Crownbay
tree/branch:Poky/denzil 
commit: 35196ff703726addf7f4051ee09d70bf9ee0c5d0
tree/branch:meta-intel/master
commit: 8024d571900fb1244316ec96dd867fcb4cedfc89

meta-intel  gitinfo: edison:34478f24de65dd8de8a4c8b913a1458d82dac1fa
Images location: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120423-1/machines/crownbay/core-image-sato-sdk-crownbay.hddimg

The system can resume from S3(standby) mode automatically. this issue existed in previous crownbay image.

Reproduce Steps:
1.Download crownbay image and install it.
2.Boot up crownbay 
3.Run command "echo mem > /sys/power/state" to make system into S3 mode.
4.wait for fan to stop, then press power button to resume.
5.redo step3, system can resume automatically after a while.
Comment 1 Darren Hart 2012-05-02 16:51:59 UTC 
You mean it will resume without any user input?
Comment 2 Darren Hart 2012-05-02 16:52:41 UTC 
.
Comment 3 yilong, sun 2012-05-03 00:54:02 UTC 
yes, i confirm this issue many times
Comment 4 Tom Zanussi 2012-06-22 20:29:50 UTC 
Could it be WOL causing this?
Comment 5 yilong, sun 2012-06-25 01:28:59 UTC 
This is the possible reason, i disable WOL, it can enter the S3 mode successfully 
in two recent test.
Comment 6 Tom Zanussi 2012-06-26 00:14:40 UTC 
The cause of this bug was a WOL setting causing the machine to wakeup on its own, closing as expected behavior in that case and not apparently a problem otherwise.
Comment 7 yilong, sun 2012-06-26 00:56:52 UTC 
I will close this problem if it is normal next time.
Comment 8 yilong, sun 2012-07-10 01:59:14 UTC 
verified it
Comment 9 Stoicescu Cornel 2012-10-09 11:54:19 UTC 
I reproduced this in branch danny, commit: 86c9aa8081f107420cd3763d0566d779daddc2b1

image: core-image-sato-sdk-crownbay
Comment 10 Tom Zanussi 2012-10-25 23:06:13 UTC 
So this happens even if WOL is disabled?
Comment 11 Tom Zanussi 2012-10-30 21:58:08 UTC 
Need to figure out if Wake On LAN is enabled and is the reason for this problem reappearing as it did previously.
Comment 12 Stoicescu Cornel 2012-10-31 09:40:41 UTC 
Just tested yesterday and indeed with WOL disabled the system does not resume.

branch: danny
commit:27af23e65f63b41962a7cfddba9e9372d5212396
Comment 13 Stoicescu Cornel 2012-10-31 09:44:27 UTC 
The test board was renewed and I did not check the WOL settings at first. If waking up automatically when WOL is enabled is as intended, then I was wrong to reopen this.
Comment 14 Tom Zanussi 2012-10-31 14:18:59 UTC 
operating as expected for wol.