Comment 16 for bug 1292400

Revision history for this message
Andy Whitcroft (apw) wrote :

Note that these come in pairs, the udev seems to be trying to look at the device the balloon driver is trying to make, so this makes sense:

    [ 240.608612] INFO: task kworker/0:2:861 blocked for more than 120 seconds.
    [ 240.608705] INFO: task systemd-udevd:1906 blocked for more than 120 seconds.
    [ 360.633541] INFO: task kworker/0:2:861 blocked for more than 120 seconds.
    [ 360.633724] INFO: task systemd-udevd:1906 blocked for more than 120 seconds.
    [ 480.638445] INFO: task kworker/0:2:861 blocked for more than 120 seconds.
    [ 480.638628] INFO: task systemd-udevd:1906 blocked for more than 120 seconds.
    [ 600.639348] INFO: task kworker/0:2:861 blocked for more than 120 seconds.
    [ 600.639531] INFO: task systemd-udevd:1906 blocked for more than 120 seconds.
    [ 720.652251] INFO: task kworker/0:2:861 blocked for more than 120 seconds.
    [ 720.652434] INFO: task systemd-udevd:1906 blocked for more than 120 seconds.

Can you confirm whether this stops at the 720s point or does it continue indefinatly.