OpenVZ Forum


Home » General » Support » Call Traces upon CT creation
Call Traces upon CT creation [message #45765] Wed, 04 April 2012 11:07
goeldi
Messages: 92
Registered: June 2006
Member
On a Debian Node with kernel 2.6.32-5-openvz-amd64 I get these call traces when I create a container:

[20040.392122] Call Trace:
[20040.392129]  [<ffffffff81111d94>] ? ll_rw_block+0xda/0xf8
[20040.392133]  [<ffffffff81066877>] ? bit_waitqueue+0x10/0xa0
[20040.392150]  [<ffffffffa010b1ac>] ? do_get_write_access+0x22c/0x444 [jbd2]
[20040.392154]  [<ffffffff81066984>] ? wake_bit_function+0x0/0x23
[20040.392160]  [<ffffffffa010b3e6>] ? jbd2_journal_get_write_access+0x22/0x33 [jbd2]
[20040.392172]  [<ffffffffa015383e>] ? __ext4_journal_get_write_access+0x4e/0x56 [ext4]
[20040.392180]  [<ffffffffa0131cd5>] ? ext4_new_inode+0x490/0xd14 [ext4]
[20040.392189]  [<ffffffffa014cd8f>] ? ext4_journal_start_sb+0xd4/0x10e [ext4]
[20040.392194]  [<ffffffffa024d846>] ? vzquota_qlnk_destroy+0x16/0xbe [vzdquota]
[20040.392202]  [<ffffffffa013c611>] ? ext4_create+0xac/0x14b [ext4]
[20040.392207]  [<ffffffff810fa72d>] ? vfs_create+0x5a/0x76
[20040.392210]  [<ffffffff810fb5bd>] ? do_filp_open+0x31b/0x8d0
[20040.392213]  [<ffffffff810f48eb>] ? cp_new_stat+0xe9/0xfc
[20040.392216]  [<ffffffff810f4ac8>] ? vfs_fstatat+0x2c/0x57
[20040.392221]  [<ffffffff8118263b>] ? strncpy_from_user+0x40/0x6d
[20040.392225]  [<ffffffff810efa5c>] ? do_sys_open+0x55/0xfc
[20040.392229]  [<ffffffff81010c12>] ? system_call_fastpath+0x16/0x1b
[20040.392232] INFO: task flush-9:5:8625 blocked for more than 120 seconds.
[20040.392238] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[20040.392247] flush-9:5     D ffff880419cfd800     0  8625      2 0x00000000
[20040.392251]  ffffffff81483c30 0000000000000046 ffffea000fbede00 ffffea000e98c9c0
[20040.392254]  ffffea000f7caa80 000000000000fa40 ffff880418dcffd8 0000000000016940
[20040.392258]  0000000000016940 ffff880419cfd800 ffff880419cfdaf8 000000000f933540
[20040.392261] Call Trace:
[20040.392264]  [<ffffffff81066877>] ? bit_waitqueue+0x10/0xa0
[20040.392268]  [<ffffffff81102639>] ? inode_wait+0x0/0xd
[20040.392270]  [<ffffffff81102642>] ? inode_wait+0x9/0xd
[20040.392275]  [<ffffffff812ea9bf>] ? __wait_on_bit+0x41/0x70
[20040.392278]  [<ffffffff8110b267>] ? inode_wait_for_writeback+0x7e/0x9e
[20040.392281]  [<ffffffff81066984>] ? wake_bit_function+0x0/0x23
[20040.392285]  [<ffffffff8110c2dc>] ? wb_writeback+0x18d/0x1ab
[20040.392289]  [<ffffffff8105b84b>] ? try_to_del_timer_sync+0x63/0x6c
[20040.392292]  [<ffffffff8110c4f1>] ? wb_do_writeback+0x14f/0x165
[20040.392295]  [<ffffffff8110c538>] ? bdi_writeback_task+0x31/0xaa
[20040.392299]  [<ffffffff810cc494>] ? bdi_start_fn+0x0/0xd0
[20040.392302]  [<ffffffff810cc504>] ? bdi_start_fn+0x70/0xd0
[20040.392305]  [<ffffffff810cc494>] ? bdi_start_fn+0x0/0xd0
[20040.392307]  [<ffffffff8106668a>] ? kthread+0xc0/0xca
[20040.392310]  [<ffffffff81011c6a>] ? child_rip+0xa/0x20
[20040.392313]  [<ffffffff810665ca>] ? kthread+0x0/0xca
[20040.392316]  [<ffffffff81011c60>] ? child_rip+0x0/0x20
[20040.392319] INFO: task vzquota:8690 blocked for more than 120 seconds.
[20040.392325] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[20040.392334] vzquota       D ffff88041c346000     0  8690   8674 0x00000000
[20040.392337]  ffff88041d0db800 0000000000000082 0000000000000000 ffff8803b0a3b9e0
[20040.392341]  ffffffff810b88cf 000000000000fa40 ffff8803f4481fd8 0000000000016940
[20040.392344]  0000000000016940 ffff88041c346000 ffff88041c3462f8 0000000100001000
[20040.392348] Call Trace:
[20040.392351]  [<ffffffff810b88cf>] ? mempool_free_slab+0x0/0xe
[20040.392355]  [<ffffffff8106de13>] ? ktime_get_ts+0x68/0xb2
[20040.392358]  [<ffffffff810168f7>] ? read_tsc+0xa/0x20
[20040.392362]  [<ffffffff8109be86>] ? delayacct_end+0x74/0x7f
[20040.392365]  [<ffffffff810b6ff1>] ? sync_page+0x0/0x46
[20040.392368]  [<ffffffff812ea495>] ? io_schedule+0x9b/0xfc
[20040.392371]  [<ffffffff810b7032>] ? sync_page+0x41/0x46
[20040.392374]  [<ffffffff812ea9bf>] ? __wait_on_bit+0x41/0x70
[20040.392377]  [<ffffffff810b71b6>] ? wait_on_page_bit+0x6b/0x71
[20040.392380]  [<ffffffff81066984>] ? wake_bit_function+0x0/0x23
[20040.392383]  [<ffffffff810bf03a>] ? pagevec_lookup_tag+0x1a/0x21
[20040.392386]  [<ffffffff810b794e>] ? wait_on_page_writeback_range+0x69/0x11b
[20040.392390]  [<ffffffff8101172e>] ? apic_timer_interrupt+0xe/0x20
[20040.392393]  [<ffffffff8110b3c1>] ? writeback_single_inode+0x13a/0x2da
[20040.392396]  [<ffffffff8110b585>] ? sync_inode+0x24/0x30
[20040.392400]  [<ffffffffa024f18a>] ? __vzquota_sync_list+0xd6/0x133 [vzdquota]
[20040.392404]  [<ffffffff8117ba07>] ? kobject_get+0x12/0x17
[20040.392408]  [<ffffffffa024f5f8>] ? do_vzquotactl+0x411/0x6ed [vzdquota]
[20040.392412]  [<ffffffff810f3ff2>] ? chrdev_open+0x0/0x13e
[20040.392415]  [<ffffffff810efcd8>] ? __dentry_open+0x1aa/0x2a5
[20040.392418]  [<ffffffff810fb780>] ? do_filp_open+0x4de/0x8d0
[20040.392422]  [<ffffffffa024d1ef>] ? vzquota_ioctl+0x4c/0x8b [vzdquota]
[20040.392426]  [<ffffffffa02041cd>] ? vzctl_ioctl+0x39/0x54 [vzdev]
[20040.392429]  [<ffffffff810fd252>] ? vfs_ioctl+0x21/0x6c
[20040.392431]  [<ffffffff810fd7a0>] ? do_vfs_ioctl+0x48d/0x4cb
[20040.392434]  [<ffffffff8118263b>] ? strncpy_from_user+0x40/0x6d
[20040.392437]  [<ffffffff810e7901>] ? virt_to_head_page+0x9/0x2a
[20040.392440]  [<ffffffff810fd81b>] ? sys_ioctl+0x3d/0x5c
[20040.392443]  [<ffffffff81010c12>] ? system_call_fastpath+0x16/0x1b

[Updated on: Wed, 04 April 2012 11:08]

Report message to a moderator

Previous Topic: Problem tracking down hardware issue
Next Topic: grsec + openvz
Goto Forum:
  


Current Time: Sat Aug 24 23:25:30 GMT 2024

Total time taken to generate the page: 0.03367 seconds