Jordan Crouse wrote: > > Breaks on the Geode - original behavior. > > I think that having boot_prams.e820_entries != 0 makes the kernel > assume the e820 data is correct. >
Okay, now I'm utterly baffled how 2.6.22 ever worked on this Geode, because this, to the best of my reading, mimics the 2.6.22 behavior exactly. DID IT REALLY, and/or did you make any kind of configuration changes? >> I want to emphasize that this is seriously broken. Using a partial e820 >> map could have disastrous results, since the kernel will have partial >> memory map information and not know about reserved areas, etc. Part of >> me feels that the right thing to do is what the current git kernel does >> -- either fall back to e801, or stop and error. > > I'm inclined to agree. Arguably the right thing to do is to find the responsible BIOS engineer and shoot them, but that's hard to do without robotics. -hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/