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 9060921B00DC1 for ; Fri, 17 Nov 2017 03:02:28 -0800 (PST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id EADAD82047; Fri, 17 Nov 2017 16:39:36 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id CA29C8204A; Fri, 17 Nov 2017 16:39:36 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Fri, 17 Nov 2017 16:39:36 +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; Fri, 17 Nov 2017 16:36:31 +0530 From: Karunakar P To: "'Wu, Jiaxin'" , "'edk2-devel@lists.01.org'" CC: "Fu, Siyuan" , "Ye, Ting" Thread-Topic: SCT Test crashes After HTTPS boot success. Thread-Index: AdNetw87ERZA5RTMTjO2Kk3mB+3gDwAg7MVgAAyVDaAAADmV4AAJhNug Date: Fri, 17 Nov 2017 11:06:31 +0000 Message-ID: References: <895558F6EA4E3B41AC93A00D163B727416348F70@SHSMSX103.ccr.corp.intel.com> <895558F6EA4E3B41AC93A00D163B7274163492F8@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <895558F6EA4E3B41AC93A00D163B7274163492F8@SHSMSX103.ccr.corp.intel.com> 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-23470.006 X-TM-AS-Result: No--25.221-5.0-31-10 X-imss-scan-details: No--25.221-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1600-8.1.1062-23470.006 X-TMASE-Result: 10--25.221100-10.000000 X-TMASE-MatchedRID: hwsFDxVJcFkcYHsGkuuPpQKDWtq/hHcNWjWsWQUWzVqnM8DdMpVuWGrr AGyO72KPGk47jFuhhjojk/kPI8DPxxiQc5OixN2z7T+j7/gPsPMfOdo4H355iG3D6f6IpbLIz1r LcNpRkyjq0MsVSwcicYTgKQZED8as6vprxL/hRbPhG1IOMb7PsFjyZ+FJjLlSgrAXgr/AjP16hG 9KQqk/+CTnW25Ruked5RzRTK2PoABocr5vRHCIamgws6g0ewz2GONdWZmbTqbaqqH/oHw+kXa9T UuI5VgR6BV3Fcs4gT18SCKVahhnrIxOAnnhEoAzqugjp/x3Owm5JJEy92I4jIEajP9ObdS0STm/ H7pw7yoPNXaBlrg+U47B35LuqeIA+OZQs4fQ6bO8coKUcaOOvTTbofuc5kuvzED5fC5RDhrv/72 zC4hJFZ3woJ2UeuYF6HMoliKXreijlFSgXWPWuPU1Xpm2N12S/AZW18vjv1o6iP0NczjR0lvr9J ucnAavzkH/0tV77RAZttB2H+RMvwkbnmLrKdcc+KUzuemidPxfohHCqSnabhUZTfM00s4+EQGwS USHP04xxoVirDGCyAUwPZNwGcXhto7DfGoLiry4E8q66ZPDHAreImldQ5BDBOjNWLXF+rxl5Iqz gSm579l9DHcHloy4klPOPDP4bOiuEAHkLyBnqjTR2TFg0xG3yiBjGmb09NuISI683skDCmYoPMJ 88H/5YIsEu4XXNvvaKWEBAQx83Zr8q/DaK2EqngIgpj8eDcBpkajQR5gb3qbyPFGTn+O49zw4lz v7RUkXnNprp3a9NjSG6JZsn1t2nuSnaYRE16hOa2goDGNvZWg25Nk4/Zon 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: Re: 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: Fri, 17 Nov 2017 11:02:29 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Jiaxin, It happens in DEBUG MODE Thanks, Karunakar From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com] Sent: Friday, November 17, 2017 12:05 PM To: Karunakar P; 'edk2-devel@lists.01.org' Cc: Fu, Siyuan; Ye, Ting Subject: RE: SCT Test crashes After HTTPS boot success. I will try to reproduce the issue with EDK2 trunk code, then feedback to yo= u. Thanks the report. Jiaxin From: Karunakar P [mailto:karunakarp@amiindia.co.in] Sent: Friday, November 17, 2017 2:32 PM To: Wu, Jiaxin >; 'edk2-dev= el@lists.01.org' > Cc: Fu, Siyuan >; Ye, Ting = > Subject: RE: SCT Test crashes After HTTPS boot success. Hi Jiaxin, Below are the detailed steps for SCT test [Steps to reproduce] . 5. Run SCT test a. Execute the following commands to run SCT test on SUT sct -r sct -u b. In Test Case Management page, Enable GenericTest c. Press F9 to run the selected test case [Observation] synchronous exception occurred in SCT ,Attached the Log for reference. Thanks, Karunakar From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com] Sent: Friday, November 17, 2017 6:01 AM To: Karunakar P; 'edk2-devel@lists.01.org' Cc: Fu, Siyuan; Ye, Ting Subject: RE: SCT Test crashes After HTTPS boot success. Hi Karunakar, Can you provide more detailed info for the SCT test steps? The crash can ha= ppen after "Sct.efi -u" or need run any specific test case? Thanks, Jiaxin From: Karunakar P [mailto:karunakarp@amiindia.co.in] Sent: Thursday, November 16, 2017 4:48 PM To: 'edk2-devel@lists.01.org' > Cc: Wu, Jiaxin >; Fu, Siyua= n >; Ye, Ting > Subject: SCT Test crashes After HTTPS boot success. 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