From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [14.98.235.2]) by mx.groups.io with SMTP id smtpd.web09.5117.1612838318842463040 for ; Mon, 08 Feb 2021 18:38:39 -0800 Authentication-Results: mx.groups.io; dkim=missing; spf=none, err=SPF record not found (domain: amiindia.co.in, ip: 14.98.235.2, mailfrom: sivaramann@amiindia.co.in) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 917EE82047; Tue, 9 Feb 2021 08:17:00 +0530 (IST) Received: from IMSVA.IN.MEGATRENDS.COM (IMSVA.IN.MEGATRENDS.COM [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B069782046; Tue, 9 Feb 2021 08:16:59 +0530 (IST) Received: from webmail.amiindia.co.in (venus2.in.megatrends.com [10.0.0.7]) by IMSVA.IN.MEGATRENDS.COM (Postfix) with ESMTPS; Tue, 9 Feb 2021 08:16:59 +0530 (IST) Received: from VENUS1.in.megatrends.com ([fe80::951:7975:6ecf:eae5]) by Venus2.in.megatrends.com ([fe80::2002:4a07:4f17:c09b%14]) with mapi id 14.03.0248.002; Tue, 9 Feb 2021 08:08:31 +0530 From: "Sivaraman Nainar" To: "Rabeda, Maciej" , "devel@edk2.groups.io" , "mcb30@ipxe.org" Subject: Re: [edk2-devel] reg: iPxe Boot in NetworkPkg Thread-Topic: [edk2-devel] reg: iPxe Boot in NetworkPkg Thread-Index: Adb6sQGLxc0HIEivTjGc7DXVtndaZgDltk4MABEn6bA= Date: Tue, 9 Feb 2021 02:38:30 +0000 Message-ID: References: <34e69419-42d8-f21f-da9b-8b506ac371c4@ipxe.org> <95e7d9c9-abf3-e23f-7989-55e99ad23983@linux.intel.com> In-Reply-To: <95e7d9c9-abf3-e23f-7989-55e99ad23983@linux.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.0.3.97] MIME-Version: 1.0 X-TM-AS-GCONF: 00 X-TM-AS-Product-Ver: IMSVA-9.1.0.1817-8.6.0.1013-25962.004 X-TM-AS-Result: No--13.484-5.0-31-10 X-imss-scan-details: No--13.484-5.0-31-10 X-TMASE-Version: IMSVA-9.1.0.1817-8.6.1013-25962.004 X-TMASE-Result: 10--13.484100-10.000000 X-TMASE-MatchedRID: PL66URbwWA/Zfnct5UBzcQLiZxZUfodHAp+UH372RZUrxUs8Nw/2fnLU dVndJEH4e4tOZAeRJf4oOuoRSi2ddS9OQltRmiCaMB2m5K0KuIlR3sGN+j7mNGOMyb1Ixq8VPfn hVjQEqGUDd0K3M8dDJf6DDthgzwn1MbO7pRnSf76seLhOr9XBOkyQ5fRSh265rt60L/HZvOWzUq 0RHquLpjltpprfZkUfj1sd/ENaiJtiUCvcCCdttao2fOuRT7aaTECLvGSdxSqTU3CLdU2O77wdQ ZVb4wHY+F5HK+bkIjuuQ6I+8huFgptfgr8OpXQ1UIJW4+Og/QK2InV6AaP6lQ+XMlIFkG/V73/E dKOTOtcha/Oaa/N+dtUwURXmb4b1B8QufIu28s5yFiJvyj8nUIIA1xEih5kwMZC3ZFuwuapKxTz SdyGhgVjkSH9LOiJW/HSjmpzXXR4kTAo7NwTzRZTaJnWciFiifrTt+hmA5bLvJUJocp0YsdgkhF 15418r4vM1YF6AJbZYoPZAqTBHwlZ0V5tYhzdWxEHRux+uk8h+ICquNi0WJPTQXHeKEJOKyXhQ0 eucclY36nEc1mPvEGOOvYvWsxf9ftwZ3X11IV0= X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Maciej: I am checking with the customer on the real use case.=20 I understand the customer is trying to run reboot test for 1000 times with= Network Enabled and I am waiting to know why the network chain loading is = enabled. -Siva -----Original Message----- From: Rabeda, Maciej [mailto:maciej.rabeda@linux.intel.com]=20 Sent: Monday, February 8, 2021 11:56 PM To: devel@edk2.groups.io; mcb30@ipxe.org; Sivaraman Nainar Subject: Re: [edk2-devel] reg: iPxe Boot in NetworkPkg Siva, Just as Michael mentioned - the log you have provided suggests that you ar= e 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=20 >> ipxe.efi as boot file. >> >> When iPXE.efi is set as boot file once it downloaded it again starts,= =20 >> it does the download and start of iPXE continuously and at some point= =20 >> it asserts in MNP Driver. > > Do you mean that you have set up an infinite loop in which UEFI loads=20 > ipxe.efi which loads ipxe.efi which loads ipxe.efi which loads=20 > ipxe.efi etc....? > > If so, then my guess is that you are simply running out of stack=20 > space. As far as I can tell, there is no memory protection around the=20 > stack in EDK2: once you have set up any kind of infinite recursion=20 > scenario then you are guaranteed to eventually underrun the stack and=20 > start overwriting random areas of memory. > > Michael > > >=20 > >