Quoting Steve Langasek ([email protected]): > On Thu, Oct 06, 2011 at 01:20:03AM -0000, Serge Hallyn wrote: > > also see bug 833891 as a udev bug specifically for the LVM case. > > Do you mean you're already tracking the LVM case on that bug instead, and
I was, yes. I filed that one some time ago to track the hang on my own laptop. I realize there are too many open bugs on this, and we should mark some as dupes. > that in the setup you're using there is *no* use of LVM? I guess no one Yes. > told Adam that this is a different bug, because it was his LVM-based setup > that I was responding to... :) Right. > > In fact, Eduard toward the end speculated precisely the semaphore as a > > cause as you just did. > > That was Eduard's speculation, copied from the *other* bug I linked to. Right. NOTE though: The LVM authors have admonished us for calling vgscan/vgchange in a udev rule, as that has its own deadlock potential. My debdiff in bug 833891 is meant to address that. It sounds like that deadlock is separate from the speculation above. Although perhaps not - such a deadlock could explain why a semaphore in udevd is not getting Vd (since udevd never finishes its processing of that rule, but just gets killed on timeout)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/818177 Title: boot failures caused by udev race To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818177/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
