gPXE and e820 memory map issues
Michael Brown <[email protected]> Thu, 25 Sep 2008 19:51:59 +0100
| Newsgroups | gmane.network.etherboot.user,gmane.network.etherboot.devel |
|---|---|
| Message-ID | <[email protected]> |
We've just tracked down a very nasty problem with the e820 memory map mangling that has been affecting gPXE since commit 320b072 (August 18th). It turns out that some BIOSes have a bug in their implementation of INT 15,e820: they don't write the entire 20 bytes of the e820 map entry on each call. The upshot is that uninitialised stack contents can end up being incorporated into the system memory map as seen by the loaded OS. Commit 3392cfa fixes this problem; see the log message at http://git.etherboot.org/?p=gpxe.git;a=commitdiff;h=3392cfa for full details. This problem is sufficiently serious that I would encourage all users who build from source to update immediately. Thanks, Michael ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/