public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: <MohammadYounasKhan.P@Dell.com>
To: <edk2-devel@lists.01.org>
Cc: <Sriramkumar.Raju@dell.com>, <KarunakarPoosapalli@Dell.com>,
	<Shekar.Babu.S@dell.com>
Subject: Re: Regarding PXE boot NACK error.
Date: Sun, 10 Mar 2019 17:48:47 +0000	[thread overview]
Message-ID: <ed3fc9583f0f43f58f97946acf405d86@BLRX13MDC420.AMER.DELL.COM> (raw)
In-Reply-To: <bd988fc6c514421da0b34ba87610aad8@BLRX13MDC420.AMER.DELL.COM>

Hi All,

Do you have any comments on this?

Thank you,
Younas.
-----Original Message-----
From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Pathan, MohammadYounasKhan
Sent: Thursday, March 7, 2019 11:07 PM
To: edk2-devel@lists.01.org
Cc: Raju, SriramKumar; Poosapalli, Karunakar; S, Shekar Babu
Subject: [edk2] Regarding PXE boot NACK error.


[EXTERNAL EMAIL] 

Hi All,

When one of DHCP cum PXE server which is not configured properly and returns NACK.

When PxeBcDhcp4Dora() returns EFI_TIME_OUT and PxeBcSelectBootPrompt () returns EFI_NOT_FOUND, do we need to abort the DHCP transaction or not in PxeBcDiscoverBootFile()? Or should we retry?
Currently it calls PxeBcDhcp4BootInfo() to get the boot info.

PxeBcDhcp4CallBack is getting called 2 times:

Dhcp4Event: 0x1 (Dhcp4RcvdOffer)
Dhcp4Event: 0xC (Dhcp4Fail)

Do we need to retry PxeBcDhcp4CallBack() for more times even if it is Dhcp4Fail?

EfiPxeLoadFile() -> PxeBcLoadBootFile () -> PxeBcDiscoverBootFile() -> PxeBcSelectBootPrompt()

Attached the transaction debug log for reference.
Please share your comments.

Thank you,
Younas.


  reply	other threads:[~2019-03-10 17:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 17:36 Regarding PXE boot NACK error MohammadYounasKhan.P
2019-03-10 17:48 ` MohammadYounasKhan.P [this message]
2019-03-18  9:39   ` MohammadYounasKhan.P
2019-03-18 10:52     ` Tomas Pilar

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=ed3fc9583f0f43f58f97946acf405d86@BLRX13MDC420.AMER.DELL.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