On Tue, 23 Jul 2002, Zwane Mwaikambo wrote:
> Around here the machine gets a vector 0x31 (timer) interrupt on CPU0 then
> locks up since the destination cpu bitmask is 0, It also seems that the
> code is trying to use logical apic id in places instead of the physical
> apic id, i saw attempted deliveries to physical apic id 4 and 8, this can
> possibly explain the APIC receive errors people were reporting?
Correction, the logical/physical apic id problem doesn't appear to be
there with the summit patch. What i'm currently seeing is a destination of
0 with a non flat/physical destination format.
-- function.linuxpower.ca- 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 : Tue Jul 23 2002 - 22:00:42 EST