Bug 9135

Summary: [Test Case 230] standby is not working properly on NUC6i5SYH
Product: [Build System, Metadata & Runtime] BSPs Reporter: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Component: bsps-runtimeAssignee: Saul Wold <sgw>
Status: VERIFIED DUPLICATE QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium CC: cristina-danielax.agurida, yp.kernel.watcher, yp.watcher
Version: 2.1   
Target Milestone: 2.1   
Hardware: NUC   
OS: x86_64   
URL: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc3
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
dmesg log none

Description Francisco Pedraza 2016-02-18 00:58:34 UTC 
STATUS: FAILED
BUILD: 2.1_M2.rc3: 152914f2983c5d69001de1d46ce99547fa1e75fe
ENVIRONMENT: genericx86-64 on NUC
STEPS TO REPRODUCE: 
1. boot system and launch terminal; check output of "date" and launch script "continue.sh"
2. echo "mem" > /sys/power/state
3. After system go into S3 mode, move mouse or press any key to make it resume
4. Check "date" and script "continue.sh"
5. Check if application can work as normal

continue.sh as below:

#################
#!/bin/sh

i=1
while [ 0 ]
do
 echo $i
 sleep 1
 i=$((i+1))
done
#################

EXPECTED OUTCOME: Screen should resume back and script can run continuously incrementing the i's value from where it was before.

ACTUAL OUTCOME: The screen was not resumed successfully, after several tries.
Comment 1 Cristina Agurida 2016-02-18 09:12:18 UTC 
I could not reproduce this issue on my NUC (model: D54250WYK). 
Image used can be found at this link: http://autobuilder.yoctoproject.org/pub/releases/yocto-2.1_M2.rc3/machines/genericx86-64/core-image-sato-sdk-genericx86-64.hddimg 

Can you tell me the model of NUC that you use for testing? Maybe it's hardware related.
Comment 2 Francisco Pedraza 2016-02-18 18:14:13 UTC 
Created attachment 2998 [details]
dmesg log

I tried to save the logs after stand by phase but it was not saved.
Comment 3 Francisco Pedraza 2016-02-18 18:16:50 UTC 
The defect is reproducible from my side, I did a ping from another machine and the ping was properly executed, however when I tried to wake up the NUC there is not response from them, I consider this can be an issue with the driver on display.
Hardware Modem: NUC6i5SYH
Comment 4 Francisco Pedraza 2016-02-18 18:23:03 UTC 
Image downloaded from autobuilder: core-image-sato-sdk-genericx86-64.hddimg
Comment 5 Saul Wold 2016-02-18 22:26:12 UTC 
I am pretty sure this is a duplicate of 8311, also a NUC running genericx86-64, 
my best thought about this is that it's graphics related and the generic 
graphics is causing issues when used with the intel hardware.

*** This bug has been marked as a duplicate of bug 8311 ***
Comment 6 Francisco Pedraza 2016-02-19 14:39:30 UTC 
Verified. Is duplicated of 8311