public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ye, Ting" <ting.ye@intel.com>
To: Santhapur Naveen <naveens@amiindia.co.in>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: ASSERT with PXE IPv6 boot.
Date: Thu, 23 Mar 2017 05:18:16 +0000	[thread overview]
Message-ID: <BC0C045B0E2A584CA4575E779FA2C12A1A8BB1DC@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <625A2455CC232F40B0F38F05ACED6D97B69AF6A3@VENUS1.in.megatrends.com>

Hi Naveen,

Thanks for reporting this. We will have a try whether we could reproduce this issue.

Best Regards,
Ting

-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Santhapur 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 Windows 10 installers present. I've been getting ASSERT with PXE IPv6 in the following 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 != 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


  reply	other threads:[~2017-03-23  5:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 15:07 ASSERT with PXE IPv6 boot Santhapur Naveen
2017-03-23  5:18 ` Ye, Ting [this message]
2017-03-23  7:50   ` Zhang, Lubo
2017-03-23  9:47     ` Santhapur Naveen
2017-04-03  6:42     ` Santhapur Naveen
2017-04-05  9:31       ` Zhang, Lubo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BC0C045B0E2A584CA4575E779FA2C12A1A8BB1DC@SHSMSX103.ccr.corp.intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox