https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244906
--- Comment #4 from Toomas Soome <[email protected]> --- (In reply to Ruslan Garipov from comment #1) Yes, it does "help" to trigger the issue by adding a bit to loader.efi size and via some change to screen update - getting text on screen via simple text output protocol does cause memory allocation by uefi firmware. The first visible related error is memory allocation to store efi memory map just before we switch off BootServices, however simple switch to alternate memory does not chenge anything there, so it must be something more going on. My guess is that the best option still would be to hook up to gdb stub and try to catch where we are blowing up and then we also know why exactly. Right now we can only guess. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
