[Users] vzctl lockup [with Ubuntu 9.04]
Kir Kolyshkin
kir at openvz.org
Mon Sep 7 04:44:13 EDT 2009
Guys,
Please report kernel bugs to bugzilla.openvz.org -- it's the best place
for such things (unless you want to discuss such bugs with other users).
Josip Rodin wrote:
> On Tue, Jul 28, 2009 at 09:10:25PM +0100, Mark Olliver wrote:
>
>> vzctl start xxx lockups after adding ip addresses and then can not be
>> killed. The out put of strace is below as it the messages log.
>>
>> The server is ubuntu 9.04 with kernel 2.6.24.
>>
>
>
>> Jul 28 20:05:30 eu-box10 kernel: [2778415.943648] Modules linked in:
>> simfs nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc tcp_bic drbd
>> vzethdev vznetdev vzdquota vzmon ipt_REJECT vzdev xt_tcpudp
>> iptable_filter ip_tables x_tables bridge kvm_intel kvm ipmi_devintf
>> ipmi_si ipmi_msghandler video output 8021q lp parport iTCO_wdt serio_raw
>> i5000_edac iTCO_vendor_support shpchp edac_core pcspkr psmouse joydev
>> mptsas mptscsih mptbase usbhid e1000 megaraid_sas scsi_transport_sas
>> bnx2 raid10 raid456 async_xor async_memcpy async_tx xor raid1 raid0
>> multipath linear
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.036679] Pid: 31985, comm:
>> vzctl Tainted: G D 2.6.24 #12 ovz009
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.050404] RIP:
>> 0010:[<ffffffff88218a1e>]
>> [<ffffffff88218a1e>] :vzmon:alloc_ve_tty_driver+0x3e/0x110
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.069356] RSP:
>> 0018:ffff8103caf7dd38 EFLAGS: 00010286
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.080306] RAX: ffff810437233000
>> RBX: ffff810437233000 RCX: 000000000000003c
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.094909] RDX: 0000000000000000
>> RSI: 0000000000000000 RDI: ffff810437233000
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.109515] RBP: ffff8103caf7dd58
>> R08: 0000000000000000 R09: 00000000002000d0
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.124119] R10: 00000000ffffffff
>> R11: ffffffff88218a0b R12: 0000000000000000
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.138725] R13: ffff810559f68000
>> R14: ffff8107ecf70000 R15: ffffffff8076f8a0
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.153330] FS:
>> 00002b07f44f46f0(0000) GS:ffff81087d86c200(0000) knlGS:0000000000000000
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.169841] CS: 0010 DS: 0000 ES:
>> 0000 CR0: 000000008005003b
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.181658] CR2: 0000000000000000
>> CR3: 00000002c2313000 CR4: 00000000000026a0
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.196265] DR0: 0000000000000000
>> DR1: 0000000000000000 DR2: 0000000000000000
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.210871] DR3: 0000000000000000
>> DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.225477] Process vzctl (pid:
>> 31985, veid=0, threadinfo ffff8103caf7c000, task ffff8103fba74000)
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.243724] Stack:
>> ffff8103fba74000 0000000000000000 ffff8103fba74000 ffff810559f68000
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.260117] ffff8103caf7ddf8
>> ffffffff88219fdb ffff81087152a440 000000000002da9f
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.275285] ffff810559f68030
>> ffff810559f68038 ffffffff80772f80 ffffffff80772f80
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.290082] Call Trace:
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.295685]
>> [<ffffffff88219fdb>] :vzmon:real_env_create+0xdeb/0x1460
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.308893]
>> [<ffffffff8821aa49>] :vzmon:vzcalls_ioctl+0x3f9/0x560
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.321580] [__up_read+0x8f/0xb0]
>> __up_read+0x8f/0xb0
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.332012]
>> [<ffffffff8820d202>] :vzdev:vzctl_ioctl+0x52/0x78
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.344006] [do_ioctl+0x31/0xa0]
>> do_ioctl+0x31/0xa0
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.354263] [vfs_ioctl
>> +0x273/0x2e0] vfs_ioctl+0x273/0x2e0
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.365040] [sys_ioctl+0x4a/0x80]
>> sys_ioctl+0x4a/0x80
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.375474] [system_call
>> +0x7e/0x83] system_call+0x7e/0x83
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.386250]
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.389570]
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.389570] Code: f3 48 a5 48 c7
>> 80 00 01 00 00 00 00 00 00 f6 83 cc 00 00 00
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.422163] RSP
>> <ffff8103caf7dd38>
>> Jul 28 20:05:30 eu-box10 kernel: [2778416.436829] ---[ end trace
>> a1599b1d0c4702b2 ]---
>>
>
> I have just seen a similar vzctl crash also with Ubuntu 9.04 (jaunty)
> but with linux-2.6.27-openvz latest git. Debian 2.6.26-2-openvz kernel
> works fine, but .27 from git doesn't. I didn't try Ubuntu's 2.6.24 OpenVZ
> kernel. vzctl is version 3.0.22-14ubuntu2.
>
> Example behaviour here:
>
> % time sudo vzctl start 2002 # just-created test VE
> Starting VE ...
> VE is mounted
> Setting CPU units: 1000
> Configure meminfo: 65536
> VE start in progress...
>
> real 0m0.116s
> user 0m0.008s
> sys 0m0.056s
> % sudo vzctl status 2002
> VEID 2002 exist mounted running
> % ps axfw | grep '[i]'nit
> 1 ? Ss 0:05 /sbin/init
> % sudo vzctl enter 2002
> [hangs uninterruptibly]
>
> % dmesg
> [ 0.000000] Linux version 2.6.27.21 (root at thismachine) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #4 SMP Sun Jul 19 16:39:44 CEST 2009
> [...]
> [ 124.816794] warning: `vzctl' uses 32-bit capabilities (legacy support in use)
> [ 124.850055] BUG: unable to handle kernel NULL pointer dereference at 00000000
> [ 124.850617] IP: [<f899f924>] :vzmon:alloc_ve_tty_driver+0x34/0xe0
> [ 124.850665] *pde = 00000000
> [ 124.852157] Oops: 0000 [#1] SMP
> [ 124.852157] Modules linked in: binfmt_misc vboxvideo drm agpgart bridge stp bnep vzethdev vznetdev simfs vzrst vzcpt tun vzdquota vzmon vzdev xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp ipt_REJECT ip_tables x_tables video output vboxvfs lp ppdev psmouse pcspkr serio_raw i2c_piix4 vboxadd parport_pc parport pcnet32 mii
> [ 124.852157]
> [ 124.852157] Pid: 3415, comm: vzctl Not tainted (2.6.27.21 #4 briullov)
> [ 124.852157] EIP: 0060:[<f899f924>] EFLAGS: 00010286 CPU: 0
> [ 124.852157] EIP is at alloc_ve_tty_driver+0x34/0xe0 [vzmon]
> [ 124.852157] EAX: f02cf0c0 EBX: f02cf0c0 ECX: 00000030 EDX: 00000001
> [ 124.852157] ESI: 00000000 EDI: f02cf0c0 EBP: eb5f9e70 ESP: eb5f9e5c
> [ 124.852157] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0069
> [ 124.852157] Process vzctl (pid: 3415, veid: 0, ti=eb5f8000 task=f01d6880 task.ti=eb5f8000)
> [ 124.852157] Stack: eb544000 00000000 f01d6880 00000000 1c0017bf eb5f9ee0 f89a0319 c04a5c00
> [ 124.852157] 00000000 00100009 00000000 f89a1070 00000000 00000000 f01d6880 000007d2
> [ 124.852157] 00000000 00000000 eb544028 c05ec780 eb544000 eb477680 c05e98b4 c05ec780
> [ 124.852157] Call Trace:
> [ 124.852157] [<f89a0319>] ? real_env_create+0x949/0xe90 [vzmon]
> [ 124.852157] [<f89a0bb4>] ? vzcalls_ioctl+0x354/0x4d4 [vzmon]
> [ 124.852157] [<c0492da0>] ? do_page_fault+0x0/0x8d0
> [ 124.852157] [<c0490f0a>] ? error_code+0x72/0x78
> [ 124.852157] [<f899a1dd>] ? vzctl_ioctl+0x4d/0x5c [vzdev]
> [ 124.852157] [<f89a0860>] ? vzcalls_ioctl+0x0/0x4d4 [vzmon]
> [ 124.852157] [<f899a190>] ? vzctl_ioctl+0x0/0x5c [vzdev]
> [ 124.852157] [<c01c3ba8>] ? vfs_ioctl+0x28/0x80
> [ 124.852157] [<c01c3c5e>] ? do_vfs_ioctl+0x5e/0x2e0
> [ 124.852157] [<c01b5177>] ? filp_close+0x47/0x70
> [ 124.852157] [<c01c3f19>] ? sys_ioctl+0x39/0x70
> [ 124.852157] [<c0103fd6>] ? syscall_call+0x7/0xb
> [ 124.852157] =======================
> [ 124.852157] Code: b8 98 c5 62 c0 89 55 ec ba d0 00 20 00 89 5d f4 89 75 f8 89 7d fc e8 ec 39 81 c7 85 c0 89 c3 74 5d b9 30 00 00 00 89 c7 8b 75 f0 <f3> a5 c7 80 ac 00 00 00 00 00 00 00 8b 55 f0 f6 83 90 00 00 00
> [ 124.852157] EIP: [<f899f924>] alloc_ve_tty_driver+0x34/0xe0 [vzmon] SS:ESP 0069:eb5f9e5c
> [ 124.861186] ---[ end trace 85638f90ef31884b ]---
>
> Similar symptoms seem to have been reported in July by another user in:
> http://ubuntuforums.org/showthread.php?p=7566283
>
>
More information about the Users
mailing list