9860 2016-06-30 15:52:53 +0000 LAN device doesn't retrieve connection after resume from suspend state 2016-08-26 20:06:32 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-runtime 2.2 MinnowBoard Max Multiple VERIFIED FIXED Medium+ normal 2.2 M3 1 david.israelx.rodriguez.castellanos david.israelx.rodriguez.castellanos sgw yp.kernel.watcher yp.watcher david.israelx.rodriguez.castellanos --- --- Don't know oldest_to_newest 63539 0 david.israelx.rodriguez.castellanos 2016-06-30 15:52:53 +0000 STATUS: FAILED BUILD: 2.2_M1.rc2: 6f0c5537e02c59e1c8f3b08f598dc049ff8ee098 ENVIRONMENT: genericx86 - on MMAX32bit, genericx86-64 - on MMAX64bit and genericx86-64 - on NUC. STEPS TO REPRODUCE: 1. Boot the system and check internet connection is on. 2. Launch two Terminals, in Terminal 1 run ping to any valid network ip, in Terminal 2 type 'echo "mem">/sys/power/state' to go into standby mode. 4.After system go into standby mode, move mouse or press any key to make it resume. 5. Check ping status running on Terminal 1. EXPECTED OUTCOME: 5. Same ping should always work before/after standby. ACTUAL OUTCOME: Ping is interrupted. Mesage displayed "ping: sendto: Network is unreachable" 63798 1 bruce.ashfield 2016-07-11 16:45:07 +0000 Sending this to Saul, so he can find someone with the right h/w to look into this. 64964 2 david.israelx.rodriguez.castellanos 2016-08-08 20:09:20 +0000 Same result on Meta-intel 2.2 M2 commit poky : a3cad8f0e0db9b2ad62ce0f2f1b0234cb9192f56 STATUS: FAIL 65048 3 california.l.sullivan 2016-08-10 22:56:58 +0000 I can reproduce this on my MinnowBoard Turbot and NUC6. The interesting part is that I can reproduce it with any release I test with. Thus far I have tested master, krogoth, jethro, and fido, and they all reproduced the bug. I am still trying to determine if it occurs on specific hardware with any image or distro, or any hardware with our images. 65102 4 david.israelx.rodriguez.castellanos 2016-08-11 21:12:05 +0000 This was discussed with Saul Wold. This bug was not detected before, because its related TC was not specific and was misinterpreted, the TC is already fixed. As a reference Ubutu 16.04 gives the expected output as stated in Description. 65104 5 california.l.sullivan 2016-08-11 21:34:19 +0000 It appears to be related to BusyBox ping. When I add iputils to the image, which replaces BusyBox ping with GPU ping, ping continues after the resume once the ethernet NIC comes back up. 65202 6 california.l.sullivan 2016-08-15 19:22:18 +0000 In the future this test case should only be ran against core-image-full-cmdline and core-image-lsb which have iputils installed, and thus have a version of ping that will continue successfully after a resume. 65238 7 david.israelx.rodriguez.castellanos 2016-08-16 19:39:11 +0000 Verified on Master core-image-full-cmd (works well) and core-image-lsb images (take a few cycles but it reconnects itself), both passed. Corresponding TC has been modified, considering comment 6 and results. https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=232 65562 8 david.israelx.rodriguez.castellanos 2016-08-26 20:06:32 +0000 Changing status to verified.