At some point in the past, I wrote:
>> 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.
On Thu, Aug 08, 2002 at 10:56:28AM -0700, Martin J. Bligh wrote:
> I can kind of read them if I really squint, but what are you trying
> to see / fix?
It's different from 2.5.29, I can follow up with that. 2.5.29 saw all 0's,
so whatever it was that was scribbling over the MPC table and making the
ID's all 0, it's scribbling on something else now (probably mem_map).
Cheers,
Bill
-
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