> Strange thing happened when I booted the latest x86 discontigmem stuff.
> The stuff where the IO-APIC ID's showed up as zeroed out went away,
> and io_apic.c just bitched about the MPC table entries because it
> doesn't realize that physid's of IO-APIC's mean squat on this box.
>
> *AND* whatever was scribbling over that table & zeroing it out went
> away. That bug is reproducible on more garden variety machines too.
> If someone who knows how to read the IO-APIC map dumps is around,
> I've included the boot log below.
I can kind of read them if I really squint, but what are you trying to see / fix?
> ... from another run, with a printk in apic.c re: mapping the IO-APICs
> turned on:
>
> mapped IOAPIC to ffffd000 (fe800000)
> mapped IOAPIC to ffffc000 (fe801000)
> mapped IOAPIC to ffffb000 (fe840000)
> mapped IOAPIC to ffffa000 (fe841000)
> mapped IOAPIC to ffff9000 (fe880000)
> mapped IOAPIC to ffff8000 (fe881000)
> mapped IOAPIC to ffff7000 (fe8c0000)
> mapped IOAPIC to ffff6000 (fe8c1000)
Looks fine to me ... ?
M.
-
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 : Thu Aug 15 2002 - 22:00:17 EST