From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (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 742F380441 for ; Wed, 22 Mar 2017 22:18:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490246301; x=1521782301; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Kn+S7sbwlaiwCOEY0TCNXuL5nYnej9iq7V+NSjWomPU=; b=tS/2/eWOrOS0YOmadlZbRDYKuGykKy89lV4nV79Z5eetkxHatuQZnyA/ xzpE64d5h+3tL+fuACJzIZ2ZhtIomw==; Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Mar 2017 22:18:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,208,1486454400"; d="scan'208";a="69898525" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by orsmga004.jf.intel.com with ESMTP; 22 Mar 2017 22:18:20 -0700 Received: from fmsmsx111.amr.corp.intel.com (10.18.116.5) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 22 Mar 2017 22:18:20 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by fmsmsx111.amr.corp.intel.com (10.18.116.5) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 22 Mar 2017 22:18:20 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.20]) by shsmsx102.ccr.corp.intel.com ([169.254.2.88]) with mapi id 14.03.0248.002; Thu, 23 Mar 2017 13:18:17 +0800 From: "Ye, Ting" To: Santhapur Naveen , "edk2-devel@lists.01.org" Thread-Topic: ASSERT with PXE IPv6 boot. Thread-Index: AdKiVMCj7Oa4iA4EQDO0HjoGDQJfOgBP/68A Date: Thu, 23 Mar 2017 05:18:16 +0000 Message-ID: References: <625A2455CC232F40B0F38F05ACED6D97B69AF6A3@VENUS1.in.megatrends.com> In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97B69AF6A3@VENUS1.in.megatrends.com> Accept-Language: zh-CN, 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: Thu, 23 Mar 2017 05:18:21 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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