From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: None (no SPF record) identity=mailfrom; client-ip=203.199.198.232; helo=imsva.in.megatrends.com; envelope-from=karunakarp@amiindia.co.in; receiver=edk2-devel@lists.01.org Received: from IMSVA.IN.MEGATRENDS.COM (Webmail.amiindia.co.in [203.199.198.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0C77A2034EE26 for ; Thu, 16 Nov 2017 00:43:32 -0800 (PST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id E76C082047; Thu, 16 Nov 2017 14:20:42 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id CFEB682046; Thu, 16 Nov 2017 14:20:42 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Thu, 16 Nov 2017 14:20:42 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Thu, 16 Nov 2017 14:17:37 +0530 From: Karunakar P To: "'edk2-devel@lists.01.org'" CC: "Wu, Jiaxin" , "'Fu, Siyuan'" , "Ye, Ting" Thread-Topic: SCT Test crashes After HTTPS boot success. Thread-Index: AdNetw87ERZA5RTMTjO2Kk3mB+3gDw== Date: Thu, 16 Nov 2017 08:47:36 +0000 Message-ID: Accept-Language: en-GB, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.84.111] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1600-8.1.0.1062-23468.006 X-TM-AS-Result: No--21.892-5.0-31-10 X-imss-scan-details: No--21.892-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23468.006 X-TMASE-Result: 10--21.891700-10.000000 X-TMASE-MatchedRID: g2eye8Y/igH1c76/u1t0kHI4Qn4tV3TtmyqQJWNsukkcVJCT3tVgaryG Trl5AuvTFUBWNn6Ybzm0Q1C18vc1ofD8WL7IHVq/C7D4xVwcmkpA8JZETQujwmecrqZc3vabHAC UcDvcWyDp5iGZch+1zPgA2h30CXxjQ2oRSAnLD1xN3UUbIf4esktBUpQXdcXSkR4NHtUnVl4BnY NwORBzLC6DNrH3AOH1lgqt8Jwk6vKl4Agrpd+E+mZUc2jtcaSd1kqyrcMalqWObf10apLcSe//v bMLiEkVnfCgnZR65gXocyiWIpet6KOUVKBdY9a49TVembY3XZL8BlbXy+O/WjqI/Q1zONHSW+v0 m5ycBq/OQf/S1XvtEBm20HYf5Ey/CRueYusp1xz4pTO56aJ0/F+iEcKpKdpuFRlN8zTSzj4RAbB JRIc/TjHGhWKsMYLIBTA9k3AZxeG2jsN8aguKvLgTyrrpk8McCt4iaV1DkEME6M1YtcX6vGXkir OBKbnv2X0MdweWjLiSU848M/hs6K4QAeQvIGeqNNHZMWDTEbfWYI2ANOleFYWReVLwk5Wv5GpAD FtYP37i8zVgXoAltk77e4Y1xq/33FYX00nSXLg7AFczfjr/7Kysv0nN5t+SuWf6C/yke7GCNi1J VOOwKeD7DUg4VA0hjc5pwhgAxoM= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0,39:0-0 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: SCT Test crashes After HTTPS boot success. X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 08:43:33 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello All, When I do SCT test, get the below failure GenericTest\EFICompliantTest 0 0 CB6F7B77-0B15-43F7-A95B-8C7F9FD70B21 FAIL = UEFI Compliant - TLS support is required The reason for the failure is that the platform doesn't have TLS related pr= otocols installed. ->if the platform supports TLS feature then, EFI_TLS_PROTOCOL, EFI_TLS_SERV= ICE_BINDING_PROTOCOL, EFI_TLS_CONFIGURATION_PROTOCOL must be existed. -> According UEFI2.7 Spec - 28.10 EFI TLS Protocols(page-1787) The TLS consumer need locate EFI_TLS_SERVICE_BINDING_PROTOCOL and call Crea= teChild() to create a new child of EFI_TLS_PROTOCOL instance. Then use EFI_= TLS_PROTOCOL to start TLS session. After use, the TLS consumer need call De= stroyChild() to destroy it. -> Network Stack follows same in HTTPS boot. While doing IPv4/6 HTTPS boot , will locate gEfiTlsServiceBindingProtocolGu= id and call TlsServiceBindingCreateChild, So that EFI_TLS_PROTOCOL and EFI_= TLS_CONFIGURATION_PROTOCOL will be installed. So once HTTPS boot is success then TLS supported protocols exist. And if we do SCT test after HTTPS boot is success, Then TLS related failure= s should NOT happen in SCT. I've tried SCT test after HTTPS boot success, But SCT test Crashes. [Steps to reproduce] 1. Configure the HTTPS Server with EFI Shell as NBP file. 2. Connect test machine and HTTPS server with LAN cable. 3. Perform HTTPS boot in test machine 4. Once HTTPS boot is success, It will launch Shell. 5. Run SCT test [Observations] 1. SCT test was crashed and unable to continue the test. Could you please provide your comments/Suggestion on this? Thanks, Karunakar