Dear XEN-Team

I've set up a complete new VM, tested copying and backuping with following 
error again:

[ 1920.052129] INFO: task jbd2/xvda2-8:98 blocked for more than 120 seconds.
[ 1920.052143]       Not tainted 3.16.0-4-amd64 #1
[ 1920.052147] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 1920.052153] jbd2/xvda2-8    D ffff880004986e78     0    98      2 0x00000000
[ 1920.052163]  ffff880004986a20 0000000000000246 0000000000012f00 
ffff8800047ebfd8
[ 1920.052171]  0000000000012f00 ffff880004986a20 ffff8800ff3137b0 
ffff8800ff80c260
[ 1920.052179]  0000000000000002 ffffffff811d7620 ffff8800047ebc80 
ffff880002a5c7c0
[ 1920.052187] Call Trace:
[ 1920.052199]  [<ffffffff811d7620>] ? generic_block_bmap+0x50/0x50
[ 1920.052208]  [<ffffffff815114a9>] ? io_schedule+0x99/0x120
[ 1920.052214]  [<ffffffff811d762a>] ? sleep_on_buffer+0xa/0x10
[ 1920.052220]  [<ffffffff8151182c>] ? __wait_on_bit+0x5c/0x90
[ 1920.052226]  [<ffffffff811d7620>] ? generic_block_bmap+0x50/0x50
[ 1920.052232]  [<ffffffff815118d7>] ? out_of_line_wait_on_bit+0x77/0x90
[ 1920.052241]  [<ffffffff810a7e90>] ? autoremove_wake_function+0x30/0x30
[ 1920.052257]  [<ffffffffa0054b49>] ? 
jbd2_journal_commit_transaction+0xe79/0x1950 [jbd2]
[ 1920.052320]  [<ffffffff8100331e>] ? xen_end_context_switch+0xe/0x20
[ 1920.052327]  [<ffffffff810912f6>] ? finish_task_switch+0x46/0xf0
[ 1920.052331]  [<ffffffff815141a3>] ? _raw_spin_unlock_irqrestore+0x13/0x20
[ 1920.052338]  [<ffffffffa0058be2>] ? kjournald2+0xb2/0x240 [jbd2]
[ 1920.052341]  [<ffffffff810a7e60>] ? prepare_to_wait_event+0xf0/0xf0
[ 1920.052347]  [<ffffffffa0058b30>] ? commit_timeout+0x10/0x10 [jbd2]
[ 1920.052353]  [<ffffffff8108809d>] ? kthread+0xbd/0xe0
[ 1920.052357]  [<ffffffff81087fe0>] ? kthread_create_on_node+0x180/0x180
[ 1920.052361]  [<ffffffff81514958>] ? ret_from_fork+0x58/0x90
[ 1920.052365]  [<ffffffff81087fe0>] ? kthread_create_on_node+0x180/0x180
[ 2040.052128] INFO: task jbd2/xvda2-8:98 blocked for more than 120 seconds.
[ 2040.052142]       Not tainted 3.16.0-4-amd64 #1
[ 2040.052147] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 2040.052153] jbd2/xvda2-8    D ffff880004986e78     0    98      2 0x00000000
[ 2040.052163]  ffff880004986a20 0000000000000246 0000000000012f00 
ffff8800047ebfd8
[ 2040.052172]  0000000000012f00 ffff880004986a20 ffff8800ff3137b0 
ffff8800ff80c260
[ 2040.052181]  0000000000000002 ffffffff811d7620 ffff8800047ebc80 
ffff880002a5c7c0
[ 2040.052190] Call Trace:
[ 2040.052200]  [<ffffffff811d7620>] ? generic_block_bmap+0x50/0x50
[ 2040.052208]  [<ffffffff815114a9>] ? io_schedule+0x99/0x120
[ 2040.052214]  [<ffffffff811d762a>] ? sleep_on_buffer+0xa/0x10
[ 2040.052221]  [<ffffffff8151182c>] ? __wait_on_bit+0x5c/0x90
[ 2040.052227]  [<ffffffff811d7620>] ? generic_block_bmap+0x50/0x50
[ 2040.052233]  [<ffffffff815118d7>] ? out_of_line_wait_on_bit+0x77/0x90
[ 2040.052241]  [<ffffffff810a7e90>] ? autoremove_wake_function+0x30/0x30
[ 2040.052255]  [<ffffffffa0054b49>] ? 
jbd2_journal_commit_transaction+0xe79/0x1950 [jbd2]
[ 2040.052298]  [<ffffffff8100331e>] ? xen_end_context_switch+0xe/0x20
[ 2040.052305]  [<ffffffff810912f6>] ? finish_task_switch+0x46/0xf0
[ 2040.052309]  [<ffffffff815141a3>] ? _raw_spin_unlock_irqrestore+0x13/0x20
[ 2040.052314]  [<ffffffffa0058be2>] ? kjournald2+0xb2/0x240 [jbd2]
[ 2040.052319]  [<ffffffff810a7e60>] ? prepare_to_wait_event+0xf0/0xf0
[ 2040.052324]  [<ffffffffa0058b30>] ? commit_timeout+0x10/0x10 [jbd2]
[ 2040.052329]  [<ffffffff8108809d>] ? kthread+0xbd/0xe0
[ 2040.052333]  [<ffffffff81087fe0>] ? kthread_create_on_node+0x180/0x180
[ 2040.052337]  [<ffffffff81514958>] ? ret_from_fork+0x58/0x90
[ 2040.052342]  [<ffffffff81087fe0>] ? kthread_create_on_node+0x180/0x180
[ 2160.052120] INFO: task jbd2/xvda2-8:98 blocked for more than 120 seconds.
[ 2160.052135]       Not tainted 3.16.0-4-amd64 #1
[ 2160.052139] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 2160.052146] jbd2/xvda2-8    D ffff880004986e78     0    98      2 0x00000000
[ 2160.052155]  ffff880004986a20 0000000000000246 0000000000012f00 
ffff8800047ebfd8
[ 2160.052164]  0000000000012f00 ffff880004986a20 ffff8800ff3137b0 
ffff8800ff80c260
[ 2160.052173]  0000000000000002 ffffffff811d7620 ffff8800047ebc80 
ffff880002a5c7c0
[ 2160.052182] Call Trace:
[ 2160.052193]  [<ffffffff811d7620>] ? generic_block_bmap+0x50/0x50
[ 2160.052202]  [<ffffffff815114a9>] ? io_schedule+0x99/0x120
[ 2160.052209]  [<ffffffff811d762a>] ? sleep_on_buffer+0xa/0x10
[ 2160.052215]  [<ffffffff8151182c>] ? __wait_on_bit+0x5c/0x90
[ 2160.052221]  [<ffffffff811d7620>] ? generic_block_bmap+0x50/0x50
[ 2160.052230]  [<ffffffff815118d7>] ? out_of_line_wait_on_bit+0x77/0x90
[ 2160.052236]  [<ffffffff810a7e90>] ? autoremove_wake_function+0x30/0x30
[ 2160.052246]  [<ffffffffa0054b49>] ? 
jbd2_journal_commit_transaction+0xe79/0x1950 [jbd2]
[ 2160.052252]  [<ffffffff8100331e>] ? xen_end_context_switch+0xe/0x20
[ 2160.052257]  [<ffffffff810912f6>] ? finish_task_switch+0x46/0xf0
[ 2160.052262]  [<ffffffff815141a3>] ? _raw_spin_unlock_irqrestore+0x13/0x20
[ 2160.052267]  [<ffffffffa0058be2>] ? kjournald2+0xb2/0x240 [jbd2]
[ 2160.052272]  [<ffffffff810a7e60>] ? prepare_to_wait_event+0xf0/0xf0
[ 2160.052277]  [<ffffffffa0058b30>] ? commit_timeout+0x10/0x10 [jbd2]
[ 2160.052282]  [<ffffffff8108809d>] ? kthread+0xbd/0xe0
[ 2160.052286]  [<ffffffff81087fe0>] ? kthread_create_on_node+0x180/0x180
[ 2160.052290]  [<ffffffff81514958>] ? ret_from_fork+0x58/0x90
[ 2160.052293]  [<ffffffff81087fe0>] ? kthread_create_on_node+0x180/0x180

Copying and backuping the Dom0 results in no error!

Best regards, Chris Keller





-----Ursprüngliche Nachricht-----
Von: Debian Bug Tracking System [mailto:ow...@bugs.debian.org]
Gesendet: Mittwoch, 13. April 2016 11:06
An: MySign AG - Infrastrcture <infrastruct...@mysign.ch>
Betreff: Bug#820862: Acknowledgement (xen-hypervisor-4.4-amd64: Xen VM on 
Jessie freezes often with INFO: task jbd2/xvda2-8:111 blocked for more than 120 
seconds)

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message has been 
received.

Your message is being forwarded to the package maintainers and other interested 
parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Debian Xen Team 
<pkg-xen-de...@lists.alioth.debian.org<mailto:pkg-xen-de...@lists.alioth.debian.org>>

If you wish to submit further information on this problem, please send it to 
820...@bugs.debian.org<mailto:820...@bugs.debian.org>.

Please do not send mail to ow...@bugs.debian.org<mailto:ow...@bugs.debian.org> 
unless you wish to report a problem with the Bug-tracking system.

--
820862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820862
Debian Bug Tracking System
Contact ow...@bugs.debian.org<mailto:ow...@bugs.debian.org> with problems

Reply via email to