Hang while accessing CF device

Thank you for your bug report. This seems to be an issue with vol_id, so I'm assigning it to it's source package (udev).

Attach your /var/log/udev and /var/log/dmesg files from the same boot

Someone (Keybuk) recommended I kill off udevadm because it shouldn't still be running. I can't get a flash reader to work; everything but the /dev entry shows up when I plug it in (dmesg, /sys/block/sdc/); seems to be the same issue.

bluefox@icebox:~$ ps -e|grep ud
 3003 ? 00:00:01 udevd
 3009 ? 00:00:00 udevadm
15251 ? 00:04:15 pulseaudio
bluefox@icebox:~$ sudo kill 3009
bluefox@icebox:~$ ps -e|grep ud
 3003 ? 00:00:01 udevd
15251 ? 00:04:15 pulseaudio
bluefox@icebox:~$ uptime
 11:32:39 up 1 day, 1:05, 5 users, load average: 3.97, 3.60, 3.26

/var/log/udev

/var/log/dmesg

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

Yep. I plugged the device straight into another machine with 8.04 on it, pulled the pictures to a 4.1GB USB flash drive, and used that to get them on this PC. Before upgrading to 8.10 beta, the device did work on this PC (the same day, even).

This suggests the issue may be a kernel issue; yet the kernel can clearly read the partition table and understand the device. Why it utterly refuses to read it on behalf of userspace is beyond me.

Thanks Scott/John

John - Please can you provide any information requested at https://wiki.ubuntu.com/KernelTeamBugPolicies that you haven't already provided.

One more thing as well - when you try to access this device, does the whole machine become completely unresponsive for 3 minutes, or just the process trying to access it?

just theprocess
ssoorry i'm drunk

just
the
process

Thanks. Could you please provide the other information I requested?

Also, it would be great if you could run fdisk through strace, following the instructions given at https://wiki.ubuntu.com/Strace. This may show which system call it is blocking on.

Thanks

uname -a

version

dmesg.log (though you already have a copy of dmesg, this one's from this boot)

lspci -vvnn

lsusb -vv

fdisk strace

(stdout was empty)

Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

No response since last query for information. If this is still an issue, please change the status to "new".

It no longer exists in latest 9.04, sorry I hadn't seen this before.

FIX RELEASED.