2386 2012-05-02 03:12:59 +0000 [Crownbay]The system can resume from S3 standby mode automatically 2012-10-31 14:18:59 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-configuration 1.2 x86 Multiple RESOLVED NOTABUG (P3)(No QA needed) Low minor 1.3 1 yilongx.y.sun tom.zanussi corneliux.stoicescu dvhart yp.bsp.watcher yp.watcher --- --- --- oldest_to_newest 20975 0 yilongx.y.sun 2012-05-02 03:12:59 +0000 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. 21007 1 dvhart 2012-05-02 16:51:59 +0000 You mean it will resume without any user input? 21008 2 dvhart 2012-05-02 16:52:41 +0000 . 21039 3 yilongx.y.sun 2012-05-03 00:54:02 +0000 yes, i confirm this issue many times 22508 4 tom.zanussi 2012-06-22 20:29:50 +0000 Could it be WOL causing this? 22520 5 yilongx.y.sun 2012-06-25 01:28:59 +0000 This is the possible reason, i disable WOL, it can enter the S3 mode successfully in two recent test. 22567 6 tom.zanussi 2012-06-26 00:14:40 +0000 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. 22568 7 yilongx.y.sun 2012-06-26 00:56:52 +0000 I will close this problem if it is normal next time. 22924 8 yilongx.y.sun 2012-07-10 01:59:14 +0000 verified it 26417 9 corneliux.stoicescu 2012-10-09 11:54:19 +0000 I reproduced this in branch danny, commit: 86c9aa8081f107420cd3763d0566d779daddc2b1 image: core-image-sato-sdk-crownbay 26939 10 tom.zanussi 2012-10-25 23:06:13 +0000 So this happens even if WOL is disabled? 27071 11 tom.zanussi 2012-10-30 21:58:08 +0000 Need to figure out if Wake On LAN is enabled and is the reason for this problem reappearing as it did previously. 27094 12 corneliux.stoicescu 2012-10-31 09:40:41 +0000 Just tested yesterday and indeed with WOL disabled the system does not resume. branch: danny commit:27af23e65f63b41962a7cfddba9e9372d5212396 27096 13 corneliux.stoicescu 2012-10-31 09:44:27 +0000 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. 27111 14 tom.zanussi 2012-10-31 14:18:59 +0000 operating as expected for wol.