> I know the hardware sucks bad, but what's wrong with trying to work
> around the problem providing noone else is bugged by the workaround?
The reliability of the hardware is next to null. You are not able to
recover from that. You may succeed to recover from a subset of malformed
APIC messages, especially as losing an interrupt is often negligible, but
sooner or later you'll get hit by a corrupted IPI message, such as a TLB
flush and the system will either crash or produce wrong results. Note
that APIC hardware already performs consistency checks on messages
exchanged, which are capable to filter out damaged ones. If the hardware
fails to do that a message has to be seriously harmed.
Similarly you wouldn't like to work around occasional corruptions on your
host data bus, would you?
> The box already has an (overkill) 300W PSU, but yet I'm still seeing
> problems.
Too bad.
-- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +- 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/