On 11/5/09, Marco d'Itri <md@xxxxxxxx> wrote: > What could cause udevadm settle to wait even if the queue is empty? > Apparently this is fully reproducible by at least two users. > > ----- Forwarded message from Christopher Schramm <debian@xxxxxxxxxxxx> ----- > > From: Christopher Schramm <debian@xxxxxxxxxxxx> > To: Marco d'Itri <md@xxxxxxxx> > CC: 554364@xxxxxxxxxxxxxxx > > [...] > > I just tried and found out the problem also occurs when calling udevadm > in the running system. So I can comfortably debug it if you tell me how > to start. > > Output is "After the udevadm settle timeout, the events queue contains:" > with two empty lines above and three below. > > ----- End forwarded message ----- > > -- > ciao, > Marco Thanks. I should be able to reproduce and debug it, given the contents of /dev/.udev/queue.bin and /sys/kernel/uevent_seqnum. I guess it's a bug in the binary queue I wrote. This would happen if udevd was terminated, so that it didn't have a change to remove /dev/.udev/queue.bin, and if an event occurred subsequent to that. But that's always been an issue and it doesn't sound like it's whats happens here. Regards Alan -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
