2.6.31-15 and newer memory issues

[salemboot]

http://ubuntuforums.org/showthread.php?t=1344897

Among others, I have witnessed a race condition where the system begins exhausting the available ram.

The swap is hardly being used.

Work around seems to be using the 2.6.31.14 kernel originally shipped with Karmic.

System Specifications:

AMD64 Ubuntu Karmic

AMD X2 4200 dual core
1 GB Memory
160 GB PATA harddrive

Thanks for you time

[Leann Ogasawara (leannogasawara)]

Just pasting comment from forum:

"Thats it, for some reason, only happens with the latest kernel, and not with the .14 version that originally started in karmic.
Usually, my system has about 140 mb used just after boot, but when i use the latest kernel and the vbox kernel module is active, memory use skyrockets to 400-500 mb just after boot. Ive checked with gnome-system-monitor and i cant trace what process is taking all that memory, aparently none, i mean all the processes show normal numbers... My system is a core2duo on a p43 chipset asus p5qlpro, with 2gb of ram installed, and an nvidia 7900gt gfx with the binary nvidia driver. Has anyone else experienced this issue too? Any thoughts?"

[penalvch (penalvch)]

salemboot, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]