Re: spurious APIC interrupt, ayiee, should never happen

Ben Fennema (bfennema@ix.netcom.com)
Sat, 06 Jun 1998 22:48:44 -0700


MOLNAR Ingo wrote:

> sigh. yet another APIC oddity. Could you try an alternative workaround,
> could you change the setup_ExtINT_pin() function in io_apic.c:
>
> - entry.dest.logical.logical_dest = 0xff; /* all CPUs */
> + entry.dest.logical.logical_dest = 0x01; /* first CPU */
>
> does this make the messages go away?
>
> -- mingo

Yup.. the

..MP-BIOS bug: 8254 timer not connected to IO-APIC
..trying to set up timer as ExtINT ... .. (found pin 0) ... works.

lines are back, and the start of the IRQ redirect table now looks like:

NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 001 01 0 0 0 0 0 1 7 51
01 0FF 0F 0 0 0 0 0 1 1 59
02 0FF 0F 0 0 0 0 0 1 1 51

(and the error messages and the CPU1 timer interrupts are still gone)

Ben

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu