On Mon Jun 11 07:02:26 EDT 2012, [email protected] wrote: > OK, solved. This motherboard (or bios) gives the io apic an id of 0, > same as the boot processor's local apic. The unexpected aliasing > causes the lapic (virtual) address to be overwritten by the ioapic > address, so the lapic timer code is looking in the wrong place for its > registers.
though unexpected, it's not aliasing. lapics and apics have different apic id namespaces. > Erik's kernel has also had a similar fix, presumably made some time > ago - there's a 9fans post about a "wierd lapic/ioapic configuration" > which I should have spotted as a clue ... 1. may 2011, according to the dump. - erik
