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.
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.
Created attachment 2998 [details] dmesg log I tried to save the logs after stand by phase but it was not saved.
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
Image downloaded from autobuilder: core-image-sato-sdk-genericx86-64.hddimg
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 ***
Verified. Is duplicated of 8311