All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: linux-hotplug@vger.kernel.org
Subject: Debugging udevd startup time
Date: Tue, 19 May 2009 20:29:54 +0000	[thread overview]
Message-ID: <4A1316C2.4090407@pardus.org.tr> (raw)

Hi,

I wonder how can I debug the possible bottleneck(s) during the startup
of udevd?

I'm writing the $(udevadm --monitor)'s output to a log file during boot
and I have the exact events and timestamps. I really don't understand
why the whole process takes a bunch of seconds.

I'm using 2.6.30_rc6 + udev 141.

It's a typical default udev installation. (compiled with -O2),

Any help or comment on the subject would be really appreciated, I'm also
sending a link to the complete monitor.log:

http://cekirdek.pardus.org.tr/~ozan/udevmonitor.log


Thanks
Ozan Caglayan

http://www.pardus.org.tr/eng


             reply	other threads:[~2009-05-19 20:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 20:29 Ozan Çağlayan [this message]
2009-05-19 23:36 ` Debugging udevd startup time Alan Jenkins
2009-05-20  0:12 ` Kay Sievers
2009-05-20  5:54 ` Ozan Çağlayan
2009-05-20 16:25 ` Ozan Çağlayan
2009-05-20 18:19 ` Greg KH
2009-05-20 18:27 ` Kay Sievers
2009-05-20 19:25 ` Ozan Çağlayan

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=4A1316C2.4090407@pardus.org.tr \
    --to=ozan@pardus.org.tr \
    --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 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.