Re: [Xen-users] Task blocked for more than 120 seconds.

[agya naila <agya.naila@xxxxxxxxx>]

I am not sure its due to high load in my case since there is still no high load in server. I didn't run any program that have high load and no client that accessing this server. I am suspecting the hotplug script. In my xend.log here is the logs :

server1@server1:~$ sudo tail /var/log/xen/xend.log

[2013-03-13 13:04:51 1983] DEBUG (DevController:144) Waiting for 51712.

[2013-03-13 13:04:51 1983] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/4/51712/hotplug-status.

[2013-03-13 13:04:51 1983] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/4/51712/hotplug-status.

[2013-03-13 13:04:51 1983] DEBUG (DevController:642) hotplugStatusCallback 1.

[2013-03-13 13:04:51 1983] DEBUG (DevController:139) Waiting for devices irq.

[2013-03-13 13:04:51 1983] DEBUG (DevController:139) Waiting for devices vfb.

[2013-03-13 13:04:51 1983] DEBUG (DevController:139) Waiting for devices pci.

[2013-03-13 13:04:51 1983] DEBUG (DevController:139) Waiting for devices vusb.

[2013-03-13 13:04:51 1983] DEBUG (DevController:139) Waiting for devices vtpm.

[2013-03-13 13:04:51 1983] INFO (XendDomain:1225) Domain DomU (4) unpaused.

any hints ?

regards,

Agya

On Wed, Mar 6, 2013 at 4:12 PM, Aaron Cossey <aaron.cossey@xxxxxxxxx> wrote:

I've encountered this frequently due to high io load. If you have monitoring of load and io, did you see anything happen just before these errors started in the logs?

Aaron Cossey
aaron.cossey@xxxxxxxxx

On Wed, Mar 6, 2013 at 1:35 PM, agya naila <agya.naila@xxxxxxxxx> wrote:

Hi all,

Today I got problem below and my domU become unresponsive and I should restart the pc to make it running properly again. 

[  240.172092] INFO: task kworker/u:0:5 blocked for more than 120 seconds.

[  240.172110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.172376] INFO: task jbd2/xvda1-8:153 blocked for more than 120 seconds.

[  240.172388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.172610] INFO: task flush-202:0:421 blocked for more than 120 seconds.

[  240.172619] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.172946] INFO: task freeswitch:1030 blocked for more than 120 seconds.

[  240.172957] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.173215] INFO: task freeswitch:1033 blocked for more than 120 seconds.

[  240.173225] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.173454] INFO: task freeswitch:1036 blocked for more than 120 seconds.

[  240.173464] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.173670] INFO: task freeswitch:1044 blocked for more than 120 seconds.

[  240.173680] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.173828] INFO: task freeswitch:1046 blocked for more than 120 seconds.

[  240.173839] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

[  240.173986] INFO: task freeswitch:1047 blocked for more than 120 seconds.

[  240.173996] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

Does any body have clue regarding this problem?

Regards,

Agya

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users