> > yes, i was using a non SMP kernel with both apic and io_apic support
> > enabled.
>
> Ok.
> Oh your configuration options should have worked. Its more a case of working
> out now why the didnt. Knowing that it is uniprocessor apic triggered is a
> help there
I have been getting these spurious interrupt messages for a long time now with
the UP_APIC option enabled. Using interrupt-heavy things like catting logs on a vesafb
console are a pretty reliable way to trigger it.
This is on a bog-standard UP box with no IO-APIC.
It doesn't seem to affect stability at all.
regards
john
p.s. what's going on with the config options ? linus pre12 seems to get rid of the
APIC fake zero page thing and enable the local APIC on UP properly, but the config options
don't seem to have changed like in the ac tree
-- "If you're not part of the problem, you're part of the problem space." - 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/