Re: Pressing ESC from "PXE windows Boot manager" causes ASSERT

[Andrew Fish <afish@apple.com>]

Karuakar,

I thought the ASSERT usually contained the line number?

Anyway the CR macro stands for Containment Record. Usually you have a pointer into a structure and you use the CR macro to find the start of the structure. It is common for things CR to include a signature at the start of the structure. 

The ASSERT you are almost reporting is likely some kind of data corruption. Like buffer overflow, use after free, etc. But without line number info it is hard to say which one it is.

Thanks,

Andrew Fish

> On May 23, 2017, at 9:20 PM, Karunakar P <karunakarp@amiindia.co.in> wrote:
> 
> Hi All,
> 
> We have facing an issue with PXE boot.
> [Issue]
> When ESC is pressed from Windows Boot manager during PXE boot (IPv4 or IPv6) system Hangs with following ASSERT
> 
> ASSERT [DxeCore] \MdeModulePkg\Core\Dxe\Mem\Pool.c : CR has Bad Signature
> 
> [Reproduction Steps]
> 1. Perform UEFI PXEv4 or UEFI PXEv6 boot
> 2. It will start PXE boot over IPv4/6 and Downloads NBP file successfully.
>   Attached the Screenshot for the same(ScreenShot1.jpg)
> 
>   It will Displays the info like "Press ENTER for network boot service"
>   Attached Screensho(ScreenShot2.jpg)
> 
> 3. Press ENTER and then press ESC immediately to see the Windows Boot Manager Menu
>   It will list the available Operating Systems
>   Attached the screenshot(ScreenShot3.png)
> 
> 4. Press ESC to come back to Setup or next Boot option
> 
> [Result]
> System hangs with ASSERT
> 
> [Expected Result]
> On pressing ESC from Windows Boot Manager, it should come back to setup/Next boot option in boot order
> 
> Note:
> We have PXE server configured in Windows Server 2012 R2.
> 
> Please look into it.
> 
> 
> Thanks,
> karunakar
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel