From: Greg KH <greg@kroah.com>
To: Piet Delaney <piet@bluelane.com>
Cc: linux-kernel@vger.kernel.org, piet at work <piet@work.piet.net>
Subject: Re: udev taking a long time during startup
Date: Tue, 1 Aug 2006 20:37:41 -0700 [thread overview]
Message-ID: <20060802033741.GA24880@kroah.com> (raw)
In-Reply-To: <1154416586.4332.64.camel@piet2.bluelane.com>
On Tue, Aug 01, 2006 at 12:16:25AM -0700, Piet Delaney wrote:
> Hey Gang:
>
> We were wondering why there is a 60 second delay on our systems
> from the time that the kernel releases memory and the file system
> is checked.
>
> I dropped into kgdb during this period and found that an init
> script, S10udev in our case, was sleeping in sys_nanosleep()
> or sys_wait4(). Looks like thread/process S10udev forks udevstart
> which forks udev which appears to be sleeping or waiting every time
> I check in on it; Seems terribly wasteful.
You don't let us know what kernel version, or what version of udev, or
even what distro you are using. I think we need a bit more information
here :)
> udev seems to be a utility for hotplug and configured
> with /etc/udev/udev.conf. Since we have no hot plug devices
> I wonder if it really has to be called on every startup. On
> solaris the device nodes are only re-established if you boot
> with a -r option.
Yes, udev figures out what device nodes to create at boot time, it is
required if you want to use it.
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-02 3:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 7:16 udev taking a long time during startup Piet Delaney
2006-08-02 3:37 ` Greg KH [this message]
2006-08-02 8:57 ` Kay Sievers
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 5:04 Piet Delaney
2006-08-03 14:09 ` Kay Sievers
2006-08-03 15:51 ` Alexander E. Patrakov
2006-08-07 23:46 ` Piet Delaney
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=20060802033741.GA24880@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@bluelane.com \
--cc=piet@work.piet.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.