> Alan Cox pointed out this problem to me and hinted that it was an IRQ
> routing problem, i'm not sure wether it is possible to code workarounds
> which don't break normal systems though. Anyone want to use Jim as a
> guinea ping? ;)
Why to code complicated workarounds for broken firmware? It's so easy to
fix, so either bother the vendor for a fix or replace the system with a
sane one. Reading and understanding the Intel's MP spec is a day or at
most two worth of man's work. I wouldn't trust the vendor that refuses to
invest in a product even that little.
-- + 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/