Never had a slower Athlon than 1.4, but I suppose the system could be
underclocked as well;-) However, I have to think there's other stuff
happen, see below.
| >
| > I also noticed that the computer booted ok with the Debian
| > bootfloppies, which use a kernel compiled for i386. So after several
| > kernel compile/boot cycles, I found out that I had to disable K7
| > optimisation to make the system boot again.
| >
| > The mainboard is a Tyan Trinity KT-A (S2390B) with a VIA KT133A
| > chipset.
| >
| > After reading here that it may be the PSU, I upgraded my 300W PSU to a
| > 431W Enermax, which made no difference.
| >
| > The only difference I can make out between the working and the
| > non-working CPU is the internal clockspeed of the CPU and the
| > stepping (old: 2, new: 4).
|
| Heat anyone? stepping 4 hasn't seemed to be the problem, at least not
| directly
| What's the tempature difference between your 1Ghz and 1.4Ghz? both CPU
| and system? What kind of cooling do you have?
In my case, if I compile a 686 kernel it is nice and stable, while an
Athlon kernel is not. With all due respect I bet the temperature is dead
the same regardless of kernel, so I can't blame temperature.
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.
Just a data point, I believe that the problems (at least those which are
bugging me) are releated to something other than temperature.
-- bill davidsen <davidsen@tmr.com> "If I were a diplomat, in the best case I'd go hungry. In the worst case, people would die." -- Robert Lipe - 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/