I understand that you've tested upto and including 2.4.16 but that kernel
oops information is a bit dated. Please reproduce with latest 2.4.18-pre
and submit a decoded oops.
>Not overclocked. I even tried to lower the speed to 375 MHz, running 75
>MHz bus speed.
Although you're not overclocking your CPU, you're actually overclocking
most of the busses on your system now...
>The problems disappear if I disable the secondary cache, but I guess
>that is because the stress on the system decreases and not because it's
Thats because you were running an overclocked FSB, your L2 runs at a
multiple of your FSB. L2 caches are very delicate especially when
overclocked. E.g. I have a CPU (C366) which can do 600Mhz stable with the
L2 disabled and only 577 with it enabled. But losing your L2 cache slows
things _considerably_. Try running memtest86 (I believe it tests caches as
well), this definately sounds like hardware problems.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/