Ubuntu
linux package

Fresh install of Ubuntu 10.10 x86_64 2.6.35-28-server leaks memory over time.

Bug #758709 reported by mdrozdziel
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I have Ubuntu 10.10 x86_64 2.6.35-28 installed on two mirror machines. Kernel processes are slowly consuming whole available memory over time. Tooks around 10 days to eat up 4GB which leads to obvious total crash.

On the pastie below, you can check how does the slab info looks like around 24 hours prior to coming crash.

http://pastie.org/private/lmx2xhijugfi8zkic4cpsa

Its always kmalloc-192 and kmalloc-32 which are leaking the memory with the mutual proportion 6:1 (192:32). I am not really sure where to go from that point. Is there any other possible way to diagnose to cause a bit deeper?

I found out some posts from people with quite similiar issue on pretty much same hardware. The proposed solution was to disable acpi and apm, but it doesn't solved the issue on my boxes.

Any ideas much appreciated.

Hardware is from HP (DL360G5).

Debian 6 works great on the same hardware, as do Ubuntu 10.10 on other boxes. This has to be on the edge of hardware and software. No idea where to go from there. System is pretty much unusable.

I posted the same problem on stackoverflow http://serverfault.com/questions/258717/ubuntu-10-10-x86-64-2-6-35-28-possible-memory-leak-slabs-slowly-eating-memory

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-headers-2.6.35-28-server 2.6.35-28.49
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-28.49-server 2.6.35.11
Uname: Linux 2.6.35-28-server x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Tue Apr 12 14:22:27 2011
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: HP ProLiant DL360 G5
PciMultimedia:

ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-28-server root=/dev/mapper/hostname-root ro acpi=off apm=off quiet
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux
dmi.bios.date: 07/10/2009
dmi.bios.vendor: HP
dmi.bios.version: P58
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrP58:bd07/10/2009:svnHP:pnProLiantDL360G5:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL360 G5
dmi.sys.vendor: HP

Revision history for this message
mdrozdziel (mdrozdziel) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Scott White (smw12) wrote :

We have this problem as well across multiple servers. Is there any timeline on a kernel update to fix this? We cannot easily upgrade from 10.10

Revision history for this message
Zogg (zoggified) wrote :

It is still valid for kernel 2.6.35-32. Is there anybody working on this issue?

Revision history for this message
Fredrick John Berchmans (fredrickprashanth) wrote :

We are also seeing this issue with Ubuntu 10.10/Linux 2.6.35-30-server #56
It would be good to have upgrade on the 2.6..35 version which fixes the problem.
Does someone know whether this is problem is fixed in future kernels?

Revision history for this message
penalvch (penalvch) wrote :

mdrozdziel, 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 Precise via http://releases.ubuntu.com/precise/ ?

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-rc5

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.

tags: added: bios-outdated
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.