From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (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 5607221A04802 for ; Mon, 10 Apr 2017 18:34:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1491874498; x=1523410498; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=OHpfBpflzmU3Vcmuv7vD4Xca+ax0xAeh+DtrwxesNQM=; b=pJmV8vVYCURRd/ZBMMrZMq4ujEs93+l1cjZ1l6bJSx633uRHQjbIqsST VTa7oxlsXGNPoBOpbt38eA5Of8X07A==; Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Apr 2017 18:34:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,184,1488873600"; d="scan'208";a="85858566" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga005.jf.intel.com with ESMTP; 10 Apr 2017 18:34:57 -0700 Received: from fmsmsx114.amr.corp.intel.com (10.18.116.8) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 10 Apr 2017 18:34:57 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by FMSMSX114.amr.corp.intel.com (10.18.116.8) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 10 Apr 2017 18:34:56 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.117]) by SHSMSX104.ccr.corp.intel.com ([10.239.4.70]) with mapi id 14.03.0319.002; Tue, 11 Apr 2017 09:34:55 +0800 From: "Wu, Jiaxin" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: SUT hangs after performing a warm boot. Thread-Index: AdKvmR2D2uz9H6EoQWaCRRO/YaHPvwB98WiwABcyG4AAHXj40A== Date: Tue, 11 Apr 2017 01:34:54 +0000 Message-ID: <895558F6EA4E3B41AC93A00D163B7274162BF0FA@SHSMSX103.ccr.corp.intel.com> References: <625A2455CC232F40B0F38F05ACED6D97C8677114@Venus2.in.megatrends.com> <895558F6EA4E3B41AC93A00D163B7274162BEC1F@SHSMSX103.ccr.corp.intel.com> <625A2455CC232F40B0F38F05ACED6D97C8678556@Venus2.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97C8678556@Venus2.in.megatrends.com> Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDVmYjg3MzAtOTE5Ni00NTJlLWE5YTAtYTc1NmJlY2U1YjIzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjhCNjBPRHN6UFhTVHA0SUc0bzdlek9JSlFmSm5HSmtzeVZSbEZDdTl0aGc9In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: SUT hangs after performing a warm boot. 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: Tue, 11 Apr 2017 01:34:58 -0000 X-Groupsio-MsgNum: 9820 Content-Language: en-US Content-Type: multipart/mixed; boundary="_002_895558F6EA4E3B41AC93A00D163B7274162BF0FASHSMSX103ccrcor_" --_002_895558F6EA4E3B41AC93A00D163B7274162BF0FASHSMSX103ccrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Naveen, Can you help to verify whether the attached patch can resolve your issue? Thanks, Jiaxin > -----Original Message----- > From: Santhapur Naveen [mailto:naveens@amiindia.co.in] > Sent: Monday, April 10, 2017 7:31 PM > To: Wu, Jiaxin ; edk2-devel@lists.01.org > Subject: RE: SUT hangs after performing a warm boot. >=20 > Hi Jiaxin, >=20 > Below are the simple reproduction steps: >=20 > BIOS UEFI Class3 > (1) Connect LAN cable (Realtek) > (2) Do cold boot or warm boot stress (Windows 10) >=20 > Please let me know for any additional information you may need. >=20 > Thanks, > Naveen >=20 > -----Original Message----- > From: Wu, Jiaxin [mailto:jiaxin.wu@intel.com] > Sent: Monday, April 10, 2017 6:00 AM > To: Santhapur Naveen; edk2-devel@lists.01.org > Subject: RE: SUT hangs after performing a warm boot. >=20 > Hi Naveen, >=20 > As the description of Ip6NdFasterTimerTicking(), it's the time routine of= ND > module for IPv6. >=20 > Can you provide the detailed reproduce steps? >=20 > Thanks, > Jiaxin >=20 > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > > Santhapur Naveen > > Sent: Friday, April 7, 2017 8:20 PM > > To: edk2-devel@lists.01.org > > Subject: [edk2] SUT hangs after performing a warm boot. > > > > Hi all, > > > > Under NetworkPkg, in Ip6Dxe driver, what purpose does this > > function > > Ip6NdFasterTimerTicking() serve? > > Sometimes, the SUT hangs in this function (at > > bootmgfw.Entry) when booting to Windows after performing a warm boot. > > > > Thanks, > > Naveen > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel --_002_895558F6EA4E3B41AC93A00D163B7274162BF0FASHSMSX103ccrcor_ Content-Type: message/rfc822 Content-Disposition: attachment; creation-date="Tue, 11 Apr 2017 01:34:54 GMT"; modification-date="Tue, 11 Apr 2017 01:34:54 GMT" Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by shsmsx102.ccr.corp.intel.com (10.239.4.154) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 6 Apr 2017 16:58:19 +0800 Received: from orsmsx105.amr.corp.intel.com (10.22.225.132) by SHSMSX103.ccr.corp.intel.com (10.239.4.69) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 6 Apr 2017 16:58:20 +0800 Received: from orsmga005.jf.intel.com (10.7.209.41) by orsmsx105-2.jf.intel.com (10.22.225.145) with Microsoft SMTP Server id 14.3.319.2; Thu, 6 Apr 2017 01:58:17 -0700 Received: from shwdeopenpsi116.ccr.corp.intel.com ([10.239.9.5]) by orsmga005.jf.intel.com with ESMTP; 06 Apr 2017 01:58:10 -0700 From: "Zhang, Lubo" To: "edk2-devel@lists.01.org" CC: "Wu, Jiaxin" , "Ye, Ting" , "Fu, Siyuan" Subject: [patch] NetworkPkg: Fix bug related DAD issue in IP6 driver. Thread-Topic: [patch] NetworkPkg: Fix bug related DAD issue in IP6 driver. Thread-Index: AQHSrrPw9BYSWw+Dvkq2O+zzUIjFRQ== Date: Thu, 6 Apr 2017 08:58:09 +0000 Message-ID: <1491469089-36756-1-git-send-email-lubo.zhang@intel.com> Content-Language: en-US X-MS-Exchange-Organization-AuthMechanism: 10 X-MS-Exchange-Organization-AuthSource: ORSMSX105.amr.corp.intel.com X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 If we set PXEv6 as the first boot option and reboot immediately after the first successful boot, it will assert. the root cause is when we set the policy from manual to automatic in PXE driver, the ip6 Configure item size is already set to zero and other structures are also released, So it is not needed to perform DAD call back function which is invoked by Ip6ConfigSetMaunualAddress. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Zhang Lubo Cc: Wu Jiaxin Cc: Ye Ting Cc: Fu Siyuan --- NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c b/NetworkPkg/Ip6Dxe/Ip6Confi= gImpl.c index bde5982..7575b79 100644 --- a/NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c +++ b/NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c @@ -782,10 +782,14 @@ Ip6ManualAddrDadCallback ( Instance =3D (IP6_CONFIG_INSTANCE *) Context; NET_CHECK_SIGNATURE (Instance, IP6_CONFIG_INSTANCE_SIGNATURE); Item =3D &Instance->DataItem[Ip6ConfigDataTypeManualAddress]; ManualAddr =3D NULL; + if (Item->DataSize =3D=3D 0) { + return; + } + for (Index =3D 0; Index < Item->DataSize / sizeof (EFI_IP6_CONFIG_MANUAL= _ADDRESS); Index++) { // // Find the original tag used to place into the NET_MAP. // ManualAddr =3D Item->Data.ManualAddress + Index; -- 1.9.5.msysgit.1 --_002_895558F6EA4E3B41AC93A00D163B7274162BF0FASHSMSX103ccrcor_--