public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Maciej Rabeda" <maciej.rabeda@linux.intel.com>
To: devel@edk2.groups.io, mcb30@ipxe.org, sivaramann@amiindia.co.in
Subject: Re: [edk2-devel] reg: iPxe Boot in NetworkPkg
Date: Mon, 8 Feb 2021 19:25:44 +0100	[thread overview]
Message-ID: <95e7d9c9-abf3-e23f-7989-55e99ad23983@linux.intel.com> (raw)
In-Reply-To: <34e69419-42d8-f21f-da9b-8b506ac371c4@ipxe.org>

Siva,

Just as Michael mentioned - the log you have provided suggests that you 
are recurse-booting iPXE.
Next server: 10.0.84.155
Filename: ipxe.efi
tftp://10.0.84.155/ipxe.efi... ok

May I ask why?

Thanks,
Maciej

On 05-Feb-21 11:10, Michael Brown wrote:
> On 05/02/2021 08:28, Sivaraman Nainar wrote:
>> Hello Maciej:
>>
>> I met an issue when tried to do the PXE boot with keeping the 
>> ipxe.efi as boot file.
>>
>> When iPXE.efi is set as boot file once it downloaded it again starts, 
>> it does the download and start of iPXE continuously and at some point 
>> it asserts in MNP Driver.
>
> Do you mean that you have set up an infinite loop in which UEFI loads 
> ipxe.efi which loads ipxe.efi which loads ipxe.efi which loads 
> ipxe.efi etc....?
>
> If so, then my guess is that you are simply running out of stack 
> space. As far as I can tell, there is no memory protection around the 
> stack in EDK2: once you have set up any kind of infinite recursion 
> scenario then you are guaranteed to eventually underrun the stack and 
> start overwriting random areas of memory.
>
> Michael
>
>
> 
>
>


  reply	other threads:[~2021-02-08 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05  8:28 reg: iPxe Boot in NetworkPkg Sivaraman Nainar
2021-02-05 10:10 ` [edk2-devel] " Michael Brown
2021-02-08 18:25   ` Maciej Rabeda [this message]
2021-02-09  2:38     ` Sivaraman Nainar

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=95e7d9c9-abf3-e23f-7989-55e99ad23983@linux.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