-
-
Notifications
You must be signed in to change notification settings - Fork 170
Exit BootServices fails on real machine if custom memory type is used. #1375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Do you have the option to get the serial output from the real hardware? This would help to get a specific panic message. |
Unfortuantely not. I also set up a more comprehensive loader where the panic handler uses my own screen writing protocol utilizing the framebuffer I got from the GOP. It still hangs nevertheless. I did find someone facing the same issue though: StackOverflow |
The issue seems to be platform-specific and independent of the rust implementation, thus I will close it. |
Uh oh!
There was an error while loading. Please reload this page.
When allocating memory for a UEFI application using BootServices with a custom memory type, the ExitBootServices call later freezes on a real machine, but it works fine in QEMU.
Everything works as expected on the real machine as well, if
MemoryType::LOADER_DATA
is used.System Information:
Tested on: Lenovo V15 G3 IAP
CPU: 12th Gen Intel(R) Core(TM) i5-1235U
Rust Toolchain: nightly
Dependencies Used:
Source Code:
config.toml
main.rs
framebuffer.rs
Note: I'm relatively new to the UEFI and OSDev community so there might be an issue with my code itself. Please feel free to correct me if the mistake is mine.
The text was updated successfully, but these errors were encountered: