All of lore.kernel.org
 help / color / mirror / Atom feed
From: Diego Iastrubni <diegoiast@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Slow boots caused by ca520507fc15a8213334a76339a3e6d567e91ea0 (udev, inittab)
Date: Thu, 19 May 2011 14:34:28 +0300	[thread overview]
Message-ID: <BANLkTik-DyW2P62rGHM70=PYS=nBYFiRoQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinfxAON7FioeoC9scz9MF9F3fVp+w@mail.gmail.com>

On Tue, May 17, 2011 at 4:45 PM, Diego Iastrubni <diegoiast@gmail.com>
wrote:
>> Moreover the ca520507fc15a8213334a76339a3e6d567e91ea0 you're pointing
>> did not change the inittab, so I don't know how reverting could modify
>> the inittab. Are you referring to the udev startup script ?
> I reverted S10udev of course.
> How can I debug this?

I debugged it by writing "set -x" and see what is executed over RS323 and
also looking at the output of "mount".

Eventually, it seems that the delay was caused by the RAMFS not booing
mounted on /dev/ which means that udev was writing real files (about 200)
over my NFS share to my real limux machine. That *is* kinda slow....

Adding the following lines fixed it (note that this mount point is not
available is fstab!):

      grep -q "^udev $udev_root" /proc/mounts || mount -t ramfs udev
$udev_root || exit 1
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110519/e99644c3/attachment.html>

  reply	other threads:[~2011-05-19 11:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 13:19 [Buildroot] Slow boots caused by ca520507fc15a8213334a76339a3e6d567e91ea0 (udev, inittab) Diego Iastrubni
2011-05-17 13:28 ` Thomas Petazzoni
2011-05-17 13:45   ` Diego Iastrubni
2011-05-19 11:34     ` Diego Iastrubni [this message]
2011-05-19 11:47       ` Peter Korsgaard
2011-05-19 11:52         ` Diego Iastrubni
2011-05-19 11:59           ` Peter Korsgaard
2011-05-19 12:04             ` Diego Iastrubni
2011-05-26 10:17               ` Diego Iastrubni
2011-05-26 14:02                 ` Peter Korsgaard
2011-05-26 14:08                   ` Diego Iastrubni

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='BANLkTik-DyW2P62rGHM70=PYS=nBYFiRoQ@mail.gmail.com' \
    --to=diegoiast@gmail.com \
    --cc=buildroot@busybox.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.