[BUG] Panic-ked at 'assertion failed: max_phys_addr < (1 << 48) / 512'

[Stay1444]

Describe the bug
After running cargo run --release i get panicket at 'assertion failed: max_phys_addr < (1 << 48) / 512' (build success, and running in QEMU)

To Reproduce
Steps to reproduce the behavior:

1. Clone the repo
2. run it in releasemode

Expected behavior
The system boots

Screenshots

Additional information

• Architecture: x86_64
• OS: Arch Linux Kernel 6.4.1
• Build environment: linux
• QEMU version: QEMU emulator version 8.0.2
• rustc version: rustc 1.59.0-nightly (cfa4ac66c 2022-01-06)
• Commit hash: 8daca65

[tomshoo]

This apparently is a bug in the bootloader crate, which was mentioned in issue #1138, which is apparently fixed in its pull request #234. I currently have a branch that bumps up everything to the latest, and apparently, everything seems to work just fine the system seems to boot, but I still am a tad hesitant to create a PR because bumping everything to the latest might just open another can of worms.

EDIT: I delete the branch mentioned by me because it contained way too many changes and it was getting hard to trace them.

[Stay1444]

Amazing! Will check it out and see if i can contribute. Any recommendations?

[tomshoo]

Any recommendations?

I just tested it on an older toolchain and seems like bumping the version for bootloader crate to 0.9.23 seems to be enough. You can try doing that and testing even further. I unfortunately cannot ATM since it is 12:00AM here and I need to get some sleep.

[tomshoo]

This issue has been fixed in PR #25.

[danielteberian]

Thank you @tomshoo. I'm closing this issue.