Hello,
We're seeing the following on a fairly busy proxmox HV (same applies to the previous kernel).
Any idea on what's going on here ?
Aug 13 00:27:22 ovz4 kernel: Ub 179 helds 924 in kmemsize on put
Aug 13 00:27:22 ovz4 kernel: UB: leaked beancounter 179 (ffff8802bc05e140)
Aug 13 00:27:22 ovz4 kernel: Tainting kernel with flag 0xa
Aug 13 00:27:22 ovz4 kernel: Pid: 85, comm: ubcleand veid: 0 Not tainted 2.6.32-31-pve #1
Aug 13 00:27:22 ovz4 kernel: Call Trace:
Aug 13 00:27:22 ovz4 kernel: [<ffffffff81073229>] ? add_taint+0x69/0x70
Aug 13 00:27:22 ovz4 kernel: [<ffffffff810b364b>] ? leak_beancounter+0x7b/0x90
Aug 13 00:27:22 ovz4 kernel: [<ffffffff810b4abf>] ? delayed_release_beancounter+0x1ef/0x210
Aug 13 00:27:22 ovz4 kernel: [<ffffffff81099149>] ? worker_thread+0x179/0x2d0
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8109fc90>] ? autoremove_wake_function+0x0/0x40
Aug 13 00:27:22 ovz4 kernel: [<ffffffff81098fd0>] ? worker_thread+0x0/0x2d0
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8109f6f8>] ? kthread+0x88/0x90
Aug 13 00:27:22 ovz4 kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8100c3ca>] ? child_rip+0xa/0x20
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8109f670>] ? kthread+0x0/0x90
pveversion -v
proxmox-ve-2.6.32: 3.2-132 (running kernel: 2.6.32-31-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8100c3c0>] ? child_rip+0x0/0x20
We're seeing the following on a fairly busy proxmox HV (same applies to the previous kernel).
Any idea on what's going on here ?
Aug 13 00:27:22 ovz4 kernel: Ub 179 helds 924 in kmemsize on put
Aug 13 00:27:22 ovz4 kernel: UB: leaked beancounter 179 (ffff8802bc05e140)
Aug 13 00:27:22 ovz4 kernel: Tainting kernel with flag 0xa
Aug 13 00:27:22 ovz4 kernel: Pid: 85, comm: ubcleand veid: 0 Not tainted 2.6.32-31-pve #1
Aug 13 00:27:22 ovz4 kernel: Call Trace:
Aug 13 00:27:22 ovz4 kernel: [<ffffffff81073229>] ? add_taint+0x69/0x70
Aug 13 00:27:22 ovz4 kernel: [<ffffffff810b364b>] ? leak_beancounter+0x7b/0x90
Aug 13 00:27:22 ovz4 kernel: [<ffffffff810b4abf>] ? delayed_release_beancounter+0x1ef/0x210
Aug 13 00:27:22 ovz4 kernel: [<ffffffff81099149>] ? worker_thread+0x179/0x2d0
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8109fc90>] ? autoremove_wake_function+0x0/0x40
Aug 13 00:27:22 ovz4 kernel: [<ffffffff81098fd0>] ? worker_thread+0x0/0x2d0
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8109f6f8>] ? kthread+0x88/0x90
Aug 13 00:27:22 ovz4 kernel: [<ffffffff810096d2>] ? __switch_to+0xc2/0x2f0
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8100c3ca>] ? child_rip+0xa/0x20
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8109f670>] ? kthread+0x0/0x90
pveversion -v
proxmox-ve-2.6.32: 3.2-132 (running kernel: 2.6.32-31-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
Aug 13 00:27:22 ovz4 kernel: [<ffffffff8100c3c0>] ? child_rip+0x0/0x20