From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) (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 278692050A8CA for ; Wed, 5 Apr 2017 02:31:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1491384685; x=1522920685; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=8tO0nhqjvZGE5o2fFqxlfytV9RU7JRZ8WbTgSQQ86Cc=; b=BtNlYt2EBMtgkiLothtWzCK9DaI7RovNVWRGOrLd3VO5EQhYQirtQZV0 q5Z5ds0yB0deV57LXALm0gV/+mUUoQ==; Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Apr 2017 02:31:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,278,1486454400"; d="scan'208";a="1131269301" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga001.fm.intel.com with ESMTP; 05 Apr 2017 02:31:25 -0700 Received: from shsmsx101.ccr.corp.intel.com (10.239.4.153) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 5 Apr 2017 02:31:25 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.246]) by SHSMSX101.ccr.corp.intel.com ([169.254.1.193]) with mapi id 14.03.0319.002; Wed, 5 Apr 2017 17:31:23 +0800 From: "Zhang, Lubo" To: Santhapur Naveen CC: "Ye, Ting" , "edk2-devel@lists.01.org" Thread-Topic: ASSERT with PXE IPv6 boot. Thread-Index: AdKiVMCj7Oa4iA4EQDO0HjoGDQJfOgBP/68AAAUgZlAAAZGK0AIlU1pgAGpNwTA= Date: Wed, 5 Apr 2017 09:31:23 +0000 Message-ID: <7619447B08B8F74DA4FF2A813B79803B39B1FA9D@shsmsx102.ccr.corp.intel.com> References: <625A2455CC232F40B0F38F05ACED6D97B69AF6A3@VENUS1.in.megatrends.com> <7619447B08B8F74DA4FF2A813B79803B39B05AD4@shsmsx102.ccr.corp.intel.com> <625A2455CC232F40B0F38F05ACED6D97B69B7472@VENUS1.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97B69B7472@VENUS1.in.megatrends.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: ASSERT with PXE IPv6 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: Wed, 05 Apr 2017 09:31:26 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Naveen =20 Thanks for the information, we have captured the assert issue as you m= entioned. I will debug more and let you know if anything updated. Best regards Lubo -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Monday, April 03, 2017 2:43 PM To: Zhang, Lubo Cc: Ye, Ting ; edk2-devel@lists.01.org Subject: Re: [edk2] ASSERT with PXE IPv6 boot. Hi Lubo, The issue can be reproduced when we set the PXE IPv6 as first boot option = and let the system boot to it. Cancel when you get the windows Login page a= nd it boots to PXE IPv6 again. In this case, ASSERT happens. Note: we have a WDS server configured for deployment. The issue CANNOT be reproduced when we boot to setup on every reboot and s= elect the PXE IPv6 boot option. Please see if you can reproduce with this environment. We will see from ou= r side and provide you any useful information we find. Thank you, Naveen -----Original Message----- From: Santhapur Naveen=20 Sent: Thursday, March 23, 2017 2:02 PM To: 'Zhang, Lubo' Cc: Ye, Ting; edk2-devel@lists.01.org Subject: RE: ASSERT with PXE IPv6 boot. Hi Lubo, Thanks for the update. I'll debug and see for more information and let you know. Thanks, Naveen -----Original Message----- From: Zhang, Lubo [mailto:lubo.zhang@intel.com]=20 Sent: Thursday, March 23, 2017 1:21 PM To: Santhapur Naveen Cc: Ye, Ting; edk2-devel@lists.01.org Subject: RE: ASSERT with PXE IPv6 boot. Hi Naveen I have made a quick test on Denlow platform following the steps to ins= tall windows 10, but cannot reproduce. Thanks Lubo=20 -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ye, = Ting Sent: Thursday, March 23, 2017 1:18 PM To: Santhapur Naveen ; edk2-devel@lists.01.org Subject: Re: [edk2] ASSERT with PXE IPv6 boot. Hi Naveen, Thanks for reporting this. We will have a try whether we could reproduce th= is issue. Best Regards, Ting -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Sant= hapur Naveen Sent: Tuesday, March 21, 2017 11:08 PM To: edk2-devel@lists.01.org Subject: [edk2] ASSERT with PXE IPv6 boot. Hello all, I've a Windows Deployment Services PXE server supporting IPv6 with Wind= ows 10 installers present. I've been getting ASSERT with PXE IPv6 in the fo= llowing scenario. 1) Enable IPv6 Support 2) PXE Boot to Win 10 installer 3) Cancel the install process (Causes system to reboot) 4) Attempt to PXE boot. Here the system hangs on the PXE boot screen. and it ASSERTs at Ip6Dxe\Ip6ConfigImpl.c(797): Index !=3D Item->DataSize / = sizeof (EFI_IP6_CONFIG_MANUAL_ADDRESS). Your suggestions is highly appreciated. Best Regards, Naveen _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel