Hi!
> > bios-e820: 000000000009f400 @ 0000000000000000 (usable)
> > bios-e820: 0000000000000c00 @ 000000000009f400 (reserved)
> > bios-e820: 0000000003f00000 @ 0000000000100000 (usable)
> > bios-e820: 0000000003f00000 @ 0000000000100000 (usable)
> > bios-e820: 0000000000100000 @ 00000000fff00000 (reserved)
> > (at this point, it appears to be in an infinite printk loop <?>)
> >
> > I didn't spend much time looking into the printk loop, but it seems to
> > end up there, even if CONFIG_DEBUG_BUGVERBOSE is not defined, as if the
> > ".byte 0x0f,0x0b" is causing the loop to begin.
> >
> > Any ideas/suggestions/comments?
>
> Having been over the code the problem is indeed the bios reporting overlapping
> /duplicated ranges. That will cause a crash in mm/bootmem when we try and free
> the range twice.
>
> I suspect you need to add some code to take the E820 map and remove any
> overlaps from it, favouring ROM over RAM if the types disagree (for safety),
> and filter them before you register them with the bootmem in
> arch/i386/kernel/setup.c
...plus prining ?@#@&#&$ BIOS reports invalid mem map
seems like good idea, so that bios bugs are fixed.
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 07 2001 - 21:00:13 EST