From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6596] New: Slow bootup if mdev is chosen
Date: Thu, 24 Oct 2013 06:41:24 +0000 (UTC) [thread overview]
Message-ID: <bug-6596-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6596
Summary: Slow bootup if mdev is chosen
Product: buildroot
Version: 2013.08
Platform: Other
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: andreas.koop at zf.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 5090
--> https://bugs.busybox.net/attachment.cgi?id=5090
disable CONFIG_UEVENT_HELPER_PATH option
When I choose mdev my Nios II based board stalls for about two minutes during
boot up. Then it proceeds again and boots normally. I've tracked the issue
down. It's because buildroot sets CONFIG_UEVENT_HELPER_PATH to "/sbin/mdev"
during kernel configuration. When I set it to an empty string Linux (3.10.0)
boots up as usual again.
If you look at the kernel's own description of CONFIG_UEVENT_HELPER_PATH it
states it shouldn't be used today anymore since it creates a high system load
on bootup.
Mdev still works after it's startup script has been run. It writes "/sbin/mdev"
to /proc/sys/kernel/hotplug which causes the kernel to inform mdev about new
events.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-10-24 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 6:41 bugzilla at busybox.net [this message]
2013-10-24 8:19 ` [Buildroot] [Bug 6596] Slow bootup if mdev is chosen bugzilla at busybox.net
2014-02-07 8:43 ` bugzilla at busybox.net
2014-02-07 10:19 ` bugzilla at busybox.net
2014-02-09 22:17 ` bugzilla at busybox.net
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=bug-6596-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox