-
Notifications
You must be signed in to change notification settings - Fork 215
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
BIOS stage 2 subtract overflows #354
Comments
Thanks for reporting! I'm not sure what's going wrong here yet. Do you have your code online somewhere so that I can do some debugging? |
@phil-opp The branch updating my OS to use Unfortunately, it's definitely not a minimal reproduction of the crash. I did try running the tests in the |
Currently, booting using legacy BIOS doesn't work for us after updating to `bootloader` v0.11.x (see rust-osdev/bootloader#354). Also, booting using UEFI is significantly nicer --- it gets us a better memory map and a bigger framebuffer, among other things. This commit changes `inoculate` to build a UEFI boot image by default, rather than defaulting to legacy BIOS.
Currently, booting using legacy BIOS doesn't work for us after updating to `bootloader` v0.11.x (see rust-osdev/bootloader#354). Also, booting using UEFI is significantly nicer --- it gets us a better memory map and a bigger framebuffer, among other things. This commit changes `inoculate` to build a UEFI boot image by default, rather than defaulting to legacy BIOS.
I'm attempting to migrate my kernel from v0.10.x of
![image](https://user-images.githubusercontent.com/2796466/225696066-7e17915d-00cb-4513-bcdb-10c44831baec.png)
bootloader
, and after switching to v0.11.x and running in QEMU, I see a panic in the BIOS bootloader's stage 2 code:The subtract that overflows appears to be on this line:
bootloader/bios/stage-2/src/fat.rs
Lines 96 to 99 in fa87d01
I'm creating the image using
BiosBoot::create_disk_image
, and passing it to QEMU with the arguments-drive format=raw,file=/path/to/bios.img
as suggested in the documentation on creating a disk image, so I don't think anything about my configuration is particularly out of the ordinary. I can provide additional information if there's anything that would help, though.Bootloader version: 0.11.2
QEMU version:
The text was updated successfully, but these errors were encountered: