Re: SUT hangs after performing a warm boot.

["Wu, Jiaxin" <jiaxin.wu@intel.com>]

[-- Attachment #1: Type: text/plain, Size: 1819 bytes --]

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 <jiaxin.wu@intel.com>; edk2-devel@lists.01.org
> Subject: RE: SUT hangs after performing a warm boot.
> 
> Hi Jiaxin,
> 
> 	Below are the simple reproduction steps:
> 
> 	BIOS UEFI Class3
> 	(1)   Connect LAN cable (Realtek)
> 	(2)   Do cold boot or warm boot stress (Windows 10)
> 
> 	Please let me know for any additional information you may need.
> 
> Thanks,
> Naveen
> 
> -----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.
> 
> Hi Naveen,
> 
> As the description of Ip6NdFasterTimerTicking(), it's the time routine of ND
> module for IPv6.
> 
> Can you provide the detailed reproduce steps?
> 
> Thanks,
> Jiaxin
> 
> > -----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

[-- Attachment #2: Type: message/rfc822, Size: 2910 bytes --]

From: "Zhang, Lubo" <lubo.zhang@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Wu, Jiaxin" <jiaxin.wu@intel.com>, "Ye, Ting" <ting.ye@intel.com>, "Fu, Siyuan" <siyuan.fu@intel.com>
Subject: [patch] NetworkPkg: Fix bug related DAD issue in IP6 driver.
Date: Thu, 6 Apr 2017 08:58:09 +0000
Message-ID: <1491469089-36756-1-git-send-email-lubo.zhang@intel.com>

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 <lubo.zhang@intel.com>
Cc: Wu Jiaxin <jiaxin.wu@intel.com>
Cc: Ye Ting <ting.ye@intel.com>
Cc: Fu Siyuan <siyuan.fu@intel.com>
---
 NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c b/NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c
index bde5982..7575b79 100644
--- a/NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c
+++ b/NetworkPkg/Ip6Dxe/Ip6ConfigImpl.c
@@ -782,10 +782,14 @@ Ip6ManualAddrDadCallback (
   Instance   = (IP6_CONFIG_INSTANCE *) Context;
   NET_CHECK_SIGNATURE (Instance, IP6_CONFIG_INSTANCE_SIGNATURE);
   Item       = &Instance->DataItem[Ip6ConfigDataTypeManualAddress];
   ManualAddr = NULL;

+  if (Item->DataSize == 0) {
+    return;
+  }
+
   for (Index = 0; Index < Item->DataSize / sizeof (EFI_IP6_CONFIG_MANUAL_ADDRESS); Index++) {
     //
     // Find the original tag used to place into the NET_MAP.
     //
     ManualAddr = Item->Data.ManualAddress + Index;
--
1.9.5.msysgit.1