This has been my complaint ever since the 2.2.0 kernel. I did not see
a reasonably stable release until 2.2.12. I do not understand why
code with such serious reproducible problems is being introduced into
the even numbered kernels. What happened to the plan to use only the
odd numbered kernels for debugging and refinement of the code? I
never said anything because I thought the the kernel developers would
eventually get back on track after the mistakes of the 2.2.x kernels
but it has been years now and it still has not happened. I do not
wish sound un-appreciative to those that have put so much wonderful
work into the Linux kernel but this is the same thing we criticize
Microsoft for. Putting out production code that obviously is not
ready. Please lets not earn the same reputation of such commercial
companies.
By the way, The 2.4.5-ac3 kernel still fills swap and runs out of
memory during my morning NFS incremental backup. I got this message
in the syslog.
May 29 06:39:15 (none) kernel: Out of Memory: Killed process 23502
(xteevee).
For some reason xteevee is commonly the process that gets killed. My
understanding is that it is part of Xscreensaver, but it was during my
backup.
This was the output of 'free' after I got up and found the swap
completely full. By that time the memory was in a reasonable state
but the swap space is still never being released.
total used free shared buffers cached
Mem: 255960 220668 35292 292 110960 80124
-/+ buffers/cache: 29584 226376
Swap: 40124 40112 12
Configuration
-------------
AMD K6-2/450
256Mb RAM
2.4.5-ac3 Kernel compiled with egcs-1.1.2.
-
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/