The machine was up, but started acting strangely a few hours later:
Code:
Mar 19 16:40:20 vm2 kernel: WARNING: at kernel/bc/net.c:334 __ub_skb_set_charge()
Mar 19 16:40:20 vm2 kernel: Pid: 4916, comm: pvemirror Not tainted 2.6.24-2-pve #1
Mar 19 16:40:20 vm2 kernel:
Mar 19 16:40:20 vm2 kernel: Call Trace:
Mar 19 16:40:20 vm2 kernel: [<ffffffff8026637e>] ub_sock_tcp_chargesend+0x1be/0x1d0
Mar 19 16:40:20 vm2 kernel: [<ffffffff80417b1e>] copy_skb_header+0xe/0x90
Mar 19 16:40:20 vm2 kernel: [<ffffffff8046486e>] tcp_send_synack+0x12e/0x240
Mar 19 16:40:20 vm2 kernel: [<ffffffff8045f05d>] tcp_rcv_state_process+0x6cd/0xdb0
Mar 19 16:40:20 vm2 kernel: [<ffffffff804677d0>] tcp_v4_do_rcv+0x260/0x7b0
Mar 19 16:40:20 vm2 kernel: [<ffffffff804691e6>] tcp_v4_connect+0x3b6/0x700
Mar 19 16:40:20 vm2 kernel: [<ffffffff8041491d>] release_sock+0x5d/0xc0
Mar 19 16:40:20 vm2 kernel: [<ffffffff80478dda>] inet_stream_connect+0x6a/0x2f0
Mar 19 16:40:20 vm2 kernel: [<ffffffff80262b9b>] charge_dcache+0x4b/0xe0
Mar 19 16:40:20 vm2 kernel: [<ffffffff804130d6>] sys_connect+0x86/0xe0
Mar 19 16:40:20 vm2 kernel: [<ffffffff802d502f>] do_ioctl+0x2f/0xa0
Mar 19 16:40:20 vm2 kernel: [<ffffffff802d5114>] vfs_ioctl+0x74/0x2d0
Mar 19 16:40:20 vm2 kernel: [<ffffffff802d464c>] set_close_on_exec+0x3c/0xb0
Mar 19 16:40:20 vm2 kernel: [<ffffffff802484e9>] __capable+0x9/0x20
Mar 19 16:40:20 vm2 kernel: [<ffffffff8020c4ee>] system_call+0x7e/0x83
Mar 19 16:40:20 vm2 kernel: