lkml.org 
[lkml]   [2002]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectBad IO APIC entry in MP table (code change proposal)
Date
From
Hi, all
It seems that kernel is not always protected against buggy BIOSes. I discovered this fact on custom x86 board which uses Intel 7500 chipset. This chipset supports up to 8 PCI buses (two on ICH IO hub and two on each P64H2 PCI hubs). In my case all this hubs are populated on board with the exception of one channel on last P64H2 hub. Each one of these channels has it's own IO APIC, so we have one of them unused.
The BIOS configures the IO APIC table entries for each IO APIC, puts right addresses in each entry, but "forgets" to change the flag of unused IO APIC to "~MPC_APIC_USABLE". The buggy entry (excepting the base address) is empty (i.e. filled with 0xff) then placed to MP table somewhere between the good entries. Kernel initialization procedure reads this entry, warns user about bad IO APIC ID, but continues to use it (I am talking about 2.4.17 version - maybe this behavior has already changed in 2.5.x tree?). This leads to wrong IRQ assignment for devices located on IO APICS which MP table entries are behind the buggy one. IRQs are growing in numbers (above 300) and later it's impossible to register an IRQ handler for these devices, as their IRQ numbers exceed 224.
Windows runs on such board without any problem.
I think that MP table parser should be changed. The bad IO APIC entry should not be taken into account, so all the rest of devices will work as usual.
I did this in my particular case inside the MP_ioapic_info function, but I am not sure that this will work for all Linux community. Probably the mpparse.c code maintainers can do this better (Ingo? Alan?).
Anyway, I think Linux should work better than Windows in a such cases, not worse
Thanks.

Kosta Porotchkin
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:28    [W:0.032 / U:0.428 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site