public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda@ilport.com.ua>
To: Nick Warne <nick@linicks.net>, linux-kernel@vger.kernel.org
Cc: gregkh@suse.de, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.12 udev hangs at boot
Date: Mon, 20 Jun 2005 13:04:10 +0300	[thread overview]
Message-ID: <200506201304.10741.vda@ilport.com.ua> (raw)
In-Reply-To: <200506181806.49627.nick@linicks.net>

On Saturday 18 June 2005 20:06, Nick Warne wrote:
> On Saturday 18 June 2005 17:53, Jeff Garzik wrote:
> > Nick Warne wrote:
> > > New 2.6.12 build hangs at initialising udev dynamic device directory on
> > > boot.
> >
> > Did you try simply waiting a while?
> >
> > udev took a long time to initialize (30-40 seconds) for me, then
> > everything worked and the machine booted just fine.
> >
> > I've seen this on both new and old udev.  Some patience will fix things :)
> 
> Yes, I waited a while first time.  No drive activity, no nothing.  Keyboard 
> was still awake though, so it wasn't a 'crash' as such. The boot just stopped 
> there twiddling it's thumbs...
> 
> Installing the latest udev though makes the machine boot so fast I can't see 
> the 'initialising udev devices' message unless I scroll back to see in 
> console.  I thought at first I broke it, and udev wasn't working at all now 
> and was being ignored, but it is working just fine :-)
> 
> But remember, what got me was it boots fine on 2.6.11.12, insomuch I never 
> really saw the udev message away and never had to investigate it before.

udev-030 is looking for detached_state somewhere inside /sys tree,
but somewhere between 2.6.12-rc3 and -rc5 detached_state is gone.

I installed udev-058 and it fixed things.

It took me more than hour to figure out, from 02:00 to after 03:00.

Greg, any plans to distribute udev and hotplug within kernel tarballs
so that people do not need to track such changes continuously?

After all, udev is tied to /sys layout which changes with kernel
and also udev is vital for properly functioning boot process
(I mean: if udev breaks, you cannot easily debug it: your box
is unusable since lots of things gone avry like gettys not having ttys
to let you log in...).
--
vda


  parent reply	other threads:[~2005-06-20 10:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-18 12:32 2.6.12 udev hangs at boot Nick Warne
2005-06-18 13:03 ` Alistair John Strachan
2005-06-18 13:44   ` Nick Warne
2005-06-18 14:58     ` Andrew Walrond
2005-06-18 16:53 ` Jeff Garzik
2005-06-18 17:06   ` Nick Warne
2005-06-19 15:04     ` Andrew Haninger
2005-06-20 10:04     ` Denis Vlasenko [this message]
2005-06-20 10:17       ` Stefan Smietanowski
2005-06-20 11:13         ` Denis Vlasenko
2005-06-20 16:25           ` Stefan Smietanowski
2005-06-20 16:39           ` Bill Davidsen
2005-06-20 16:48       ` Greg KH
2005-06-20 17:24         ` Jeff Garzik
2005-06-20 17:34           ` Greg KH
2005-06-20 19:00             ` Nick Warne
2005-06-20 19:21               ` Greg KH
2005-06-20 19:32                 ` Nick Warne
2005-06-20 19:42                   ` David Lang
2005-06-21  6:28                     ` Greg KH
2005-06-21  6:31                       ` David Lang
2005-06-21  6:47                         ` Greg KH
2005-06-20 19:46                 ` Jesper Juhl
2005-06-20 19:34               ` Andrew Haninger
2005-06-20 19:49             ` Josh Boyer
2005-06-21  6:42               ` Greg KH
2005-06-20 19:24           ` Olaf Hering
2005-06-20 21:26         ` Daniel Barkalow
2005-06-20 22:14           ` Jesper Juhl
2005-06-20 22:26           ` Tomasz Torcz
  -- strict thread matches above, loose matches on Subject: below --
2005-06-18 15:32 Nick Warne
2005-06-21  6:40 ` Greg KH
2005-06-19 15:39 Nick Warne
2005-06-19 21:23 ` Andrew Haninger
2005-06-21  6:45 ` Greg KH
2005-06-21 17:06   ` Nick Warne

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=200506201304.10741.vda@ilport.com.ua \
    --to=vda@ilport.com.ua \
    --cc=gregkh@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox