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

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

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.

[-- Attachment #2: DebugLog.txt --]
[-- Type: text/plain, Size: 1658 bytes --]

EfiPxeLoadFile Entry
MediaStatus: Success
UsingIpv6: 0
EfiPxeBcStart Entry
Mode->UsingIpv6: 0Start PXE over IPv6
Private->Udp4Read->Configure Status: Success
PxeBcSeedDhcp4Packet Entry
PxeBcSeedDhcp4Packet Exit
CreateEvent for Arp Status: Success
SetTimer for ARP Status: Success
CreateEvent for Icmp Status: Success
PxeBcSetIp4Policy Entry
Ip4Config2->GetData Status: Success
PxeBcSetIp4Policy Exit
PxeBcSetIp4Policy Status: Success
CreateEvent for Udptimeout Status: Success
Everything is success
PxeBc->Start() Status: Success
PxeBcLoadBootFile Entry
PxeBcInstallCallback Entry
InstallProtocolInterface: 245DCA21-FB7B-11D3-8F01-00A0C969723B B4962190
PxeBcInstallCallback Exit Status: Success
PxeBcInstallCallback Status: Success
Private->BootFileSize: 0
PxeBcDiscoverBootFile Entry
EfiPxeBcDhcp Entry
Mode->UsingIpv6: 0PxeBcDhcp4Dora Entry
PxeBcBuildDhcp4Options Entry
PxeBcBuildDhcp4Options Exit Index: 0x5
OptCount: 0x5
Dhcp4->Configure Status: Success
PxeBcDhcp4CallBack Entry, Dhcp4Event: 0x1
PxeBcParseDhcp4Options Entry
Found the required option. So return the option
Callback Status: Warning Unknown Glyph
PxeBcDhcp4CallBack Exit Status: Success
PxeBcDhcp4CallBack Entry, Dhcp4Event: 0xC
returns success
Dhcp4->Start Status: Time out
PxeBcDhcp4Dora Exit Status: Time out
PxeBcDhcp4Dora Status: Time out
Private->Udp6Read->Configure Status: Success
EfiPxeBcDhcp Exit status:Success
PxeBc->Dhcp Status: Success
PxeBcSelectBootPrompt Status: Not Found
Mode->ProxyOfferReceived: 0x0
Mode->UsingIpv6: 0

DXE_ASSERT!: c:\dummy\NetworkPkg\UefiPxeBcDxe\PxeBcBoot.c (508): Cache4->OptList[6] != ((void *) 0)

             reply	other threads:[~2019-03-07 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 17:36 MohammadYounasKhan.P [this message]
2019-03-10 17:48 ` Regarding PXE boot NACK error MohammadYounasKhan.P
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=bd988fc6c514421da0b34ba87610aad8@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