> I reconfigured my kernel to lie to it and say k6 for the processor
> family instead of k7.
right. and just for posterity, let me note here that
the K7-specific kernel code IS NOT KNOWN TO BE BUGGY.
the best and so far only explanation is that since CONFIG_MK7
can *triple* the bandwidth that Linux demands of dram,
marginal hardware is pushed over the edge. stable hardware
has no problem with the code, and the code follows AMD's specs.
turning off the optimizations is just de-tuning the kernel
to pander to (work around) flakey hardware.
> > > Well, I have worked around this problem by getting rid of the Athlon
> > > optimizations so I guess there is still more work to do on those.
> >
> > Could you please tell what did you change, exactly? It might be that
> > this information should be in etc/PROBLEMS, in case other users bump into
> > the same problem.
-
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/
This archive was generated by hypermail 2b29 : Wed Jan 23 2002 - 21:01:04 EST