> > The problem I have is seen only when I use Athlon code enabled with
> > menuconfig, so the question is if the code is bad (as in timing
> > sensitive), or if the compiler might be generating bad code for Athlon.
>
> or the chipset/motherboard/dram can't handle the 2-3x bandwidth
> demanded by the athlon code in the kernel. the latter is conventional
> wisdom for the past 6-8 months.
The so-called Athlon patch fixed the problem for me on my Abit KK266R
board, I stress tested it at 146MHz FSB (10% o/c) just to see if it was
stable, and it seems all the problems have gone away in both kernel and
user land.
It could be that the bit cleared slows memory, I haven't checked to see if
playing with memory parameters will do the same thing.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- 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/