|
From: Stephen M. W. <ste...@br...> - 2006-05-04 18:41:11
|
On 04/05/06 13:15, Daniel Raffler wrote: > > It's a real IOAPIC all right. The mobo is a GA-K8VM800M (VIA chipset for > > socket 754). I suspect Gigabyte misinterpreted the IOAPIC specs, since > > they say the correct value is 11h which they may have though was in > > binary. > > As the I/O APIC is part of the chipset's south-bridge it's actually VIA > rather than Gigabyte that is to be blamed for the bug. In any case your > assumption does make some sense in my opinion, although I frankly wouldn't > have expected a global player like VIA to make such blunders. True. I have a VIA chipset in another computer (not at hand at the moment) that does not report anything unusual. Since noone seems to do much with the IO-APIC version number I don't suppose it really makes any difference. > > Note that the LAPIC address here is different that the one you > > detected. > > Actually the trion kernel doesn't even print the local APIC address, what > you posted is the location of the multiprocessor configuration table.. My mistake. I was so excitied about creating a bootable Trion CD I didn't bother checking the code tee see what I was actually writing down. Some of my test systems do not have floppies. -- Stephen M. Webb ste...@br... |