The announcement of 2.1.125 said we are quite close to 2.2.0. So I've tried
make -j zImage both with this kernel (actually 2.1.125ac2) and with
2.0.36pre13.
My experiences: under 2.0.36 everything went fine. Of course most of the
processes exited because of unsufficient memory, but my machine didn't crash.
With 2.1.125, it always crashed after about 2 or 3 minutes. Crashing means
here: the only thing I could do is switch between virtual consoles and press
alt+sysrq+key. Alt+sysrq+s and u writes "syncing" and "remounting" to the
console but actually the syncing or remounting is not done. And usually after
pressing these combinations, I've found that the alt key was stuck in. The
only way to "release" the alt key is to switch to another console and then
switch back.
I write this because I haven't heard saying that 2.1.125 is quite unstable.
Please do not release 2.2.0 until it is not as stable as 2.0.36 at heavy
loads.
I have an intel-486 machine with 32M ram and 52412K swap, but I also tried
compiling the kernel with the swap turned off, and it still worked under
2.0.36 but caused 2.1.125 to crash.
bye
Egmont Koblinger
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/