Further debugging on IRC suggests this is a problem with a connected Compat Flash device:
<bluefoxicy> Keybuk: fdisk -l /dev/sdc hangs. o_o <bluefoxicy> bluefox@icebox:~$ sudo fdisk -l /dev/sdc ^C^C^C^Z^Z ................. wow.
That is why the vol_id process is there, hanging for three minutes, after which point udev will kill it.
It's also why you have no /dev/sdc or /dev/sdc1 (the probing failed, so udev will terminate the process and not attempt to create a device node)
It's also why you still have udevadm monitor running, since it now stays running after failure for more debugging greatness
Further debugging on IRC suggests this is a problem with a connected Compat Flash device:
<bluefoxicy> Keybuk: fdisk -l /dev/sdc hangs. o_o
<bluefoxicy> bluefox@icebox:~$ sudo fdisk -l /dev/sdc
^C^C^C^Z^Z
................. wow.
That is why the vol_id process is there, hanging for three minutes, after which point udev will kill it.
It's also why you have no /dev/sdc or /dev/sdc1 (the probing failed, so udev will terminate the process and not attempt to create a device node)
It's also why you still have udevadm monitor running, since it now stays running after failure for more debugging greatness