> Yes, the hardware is at fault. I don't have money for
> other hardware though, so working around it seems a good idea.
What's the problem with using a privately patched kernel then? I do that
all the time for various stuff.
> We could simplify the IDE driver a lot by dropping support for
> all the broken controllers too. Or tell
> people to not use DMA on them.
It depends on how intrusive and reliable the workarounds are. If merely
slowing down or using PIO is sufficient, then they may be OK to include.
> The safe solution is NOAPIC, this fix simply makes it work
> for a longer time using the bad apic.
Well, consider it *the* workaround, then.
-- + 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/