From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.6.12 + devices on initrd
Date: Sun, 19 Jun 2005 15:14:09 +0000 [thread overview]
Message-ID: <42B58BC1.3020601@ums.usu.ru> (raw)
In-Reply-To: <200506191420.39355.Janne.Karhunen@gmail.com>
Janne Karhunen wrote:
> On Sunday 19 June 2005 17:37, Janne Karhunen wrote:
>
>
>>So it defaults to 5 second wait, but it really doesn't wait that
>>long. It waits less than a second prior to giving up. Umm .. what
>>could cause 'sleep' not to sleep .. umm, a signal. But where could
>>it get that? ARGH. So i'm guessing adding additional sleeps or
>>even using that 'udev_timeout' switch doesn't help.
>
>
> So much for my sense of time (once playing with Linux, anyway).
>
> Giving it 20 second timeout via udev_timeout does help, it
> goes on booting. But for some reason udev is _really_slow_ on
> creating devices with 2.6.12. Creating just that one device
> takes more than 10 seconds. Let alone when it keeps on booting
> with SUSEs highly-parallel init; udev is so slow that it seems
> to break everything :/
Sorry, I should have noticed this earlier:
> FWIW In the udev 058 announcement, Greg said:
>
> "Note, if you are running a kernel newer than 2.6.12-rc4 (including
> the -mm releases) and you have any custom udev rules, you MUST upgrade
> to the latest version to allow udev to work properly.
> This change happened
> because of a previously-unrealized reliance in libsysfs on the
> presence of a useless sysfs file that has recently been
> removed. Hopefully the libsysfs people will be releasing a new
> version shortly with this change
> in it for those packages who rely on it."
>
> Just a reminder because I bet many people will get caught out by this!
So please upgrade udev.
--
Alexander E. Patrakov
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-06-19 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 11:20 2.6.12 + devices on initrd Janne Karhunen
2005-06-19 11:37 ` Alexander E. Patrakov
2005-06-19 12:07 ` Janne Karhunen
2005-06-19 12:42 ` Alexander E. Patrakov
2005-06-19 12:48 ` Jasper Huijsmans
2005-06-19 13:10 ` Janne Karhunen
2005-06-19 13:48 ` Alexander E. Patrakov
2005-06-19 14:37 ` Janne Karhunen
2005-06-19 15:07 ` Janne Karhunen
2005-06-19 15:14 ` Alexander E. Patrakov [this message]
2005-06-19 15:53 ` Janne Karhunen
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=42B58BC1.3020601@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).