From: James Hunt <james.hunt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: udevd messages lost on exit?
Date: Fri, 30 Sep 2011 08:29:49 +0000 [thread overview]
Message-ID: <4E857DFD.2060709@ubuntu.com> (raw)
Hi All,
I'm investigating a problem in Ubuntu Oneiric where we think udev messages maybe be getting lost due
to the way that we're stopping udevd:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/818177
In summary, at the end of our initramfs, we are doing this:
# Stop udevd, we'll miss a few events while we run init, but we catch up
udevadm control --exit
# Move /dev to the real filesystem
mount -n -o move /dev ${rootmnt}/dev
The problem is that most notably when using lvm2 the "--exit" call seems to be causing udev messages
relating to the *rootfs* to be lost so that the system fails to boot.
Looking at udevd.c, it does the following when requested to exit:
/* discard queued events and kill workers */
event_queue_cleanup(udev, EVENT_QUEUED);
worker_kill(udev, 0);
I'm currently trying to debug what is left in the queue to get a better handle on this, but I am
wondering if "udevadm control --exit" should request that udevd drain the queues rather than
discarding the messages for our case. Is the reason the messages are discarded to avoid slowing down
the boot coupled with the expectation that the caller will use "udevadm trigger" to catch up later?
Kind regards,
James.
next reply other threads:[~2011-09-30 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 8:29 James Hunt [this message]
2011-09-30 9:03 ` udevd messages lost on exit? Kay Sievers
2011-09-30 9:33 ` James Hunt
2011-09-30 9:44 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E857DFD.2060709@ubuntu.com \
--to=james.hunt@ubuntu.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).