important bugfix to kernel

I thought that is already fixed in vzkernel-2.6.32-042stab108.5.src.rpm (pve-kernel-2.6.32-39-pve_2.6.32-157).
 
root@node ~ # uname -a
Linux root 2.6.32-39-pve #1 SMP Wed Jun 24 06:39:42 CEST 2015 x86_64 GNU/Linux


root@node ~ # dmesg | grep "leaked beancounter"
UB: leaked beancounter 102 (ffff880407af3340)
UB: leaked beancounter 106 (ffff8804012ee080)
UB: leaked beancounter 115 (ffff8804012eea00)
UB: leaked beancounter 5005 (ffff88031f87f440)



....


so the bug is present even in the latest PVE kernel.
please, fix it..
 
root@node ~ # pveversion -v
proxmox-ve-2.6.32: 3.4-157 (running kernel: 2.6.32-39-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
You must log in or register to reply here.
Top Bottom