From: iSteve <isteve@rulez.cz>
To: linux-hotplug@vger.kernel.org
Subject: Re: UDev startup 30-45s or more
Date: Tue, 07 Feb 2006 14:43:59 +0000 [thread overview]
Message-ID: <43E8B22F.1010702@rulez.cz> (raw)
In-Reply-To: <43E896DB.2080506@rulez.cz>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Kay Sievers wrote:
> No idea. On my 2GHz laptop, the whole coldplug with running the full setup
> for all ~400 devices and creating all nodes takes ~2 seconds until the queue
> is completely empty.
>
> Kay
After toying with the udev rules, I've managed to pinpoint it to a
single rule set; I failed to find out which rule causes it though, I
believe it may be caused by a combination of rules.
Please note that I am _not_ running a system that has PCMCIA; I want the
rules for udev to be generic, as I will run the same system on a
notebook as well. The file is composed of rules from pcmciautils
software package (for handling PCMCIA with latest kernels).
Thanks in advance for any help, it'd be nice to resolve this one:)
-- iSteve
(Please find the attached ruleset)
[-- Attachment #2: pcmcia.rules --]
[-- Type: text/plain, Size: 1101 bytes --]
# PCMCIA devices:
#
# Very few CIS firmware entries (which we use for matching)
# are so broken that we need to read out random bytes of it
# instead of the manufactor, card or product ID. Then the
# matching is done in userspace.
ACTION=="add", SUBSYSTEM=="pcmcia", MODALIAS=="?*", \
RUN+="/lib/udev/pcmcia-check-broken-cis"
# However, the "weak" matching by func_id is only allowed _after_ modprobe
# returns, so that "strong" matches have a higher priority.
ACTION=="add", SUBSYSTEM=="pcmcia", MODALIAS=="?*", \
RUN+="/bin/sh -c 'echo 1 > /sys/$devpath/allow_func_id_match'"
# modprobe $modalias loads all possibly appropriate modules
ACTION=="add", SUBSYSTEM=="pcmcia", MODALIAS=="?*", \
RUN+="/sbin/modprobe $modalias"
# PCMCIA sockets:
#
# modprobe the pcmcia bus module so that 16-bit PCMCIA devices work
ACTION=="add", SUBSYSTEM=="pcmcia_socket", \
RUN+="/sbin/modprobe -b pcmcia"
# if this is a PCMCIA socket which needs a resource database,
# pcmcia-socket-startup sets it up
ACTION=="add", SUBSYSTEM=="pcmcia_socket", \
RUN+="/lib/udev/pcmcia-socket-startup"
prev parent reply other threads:[~2006-02-07 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 12:47 UDev startup 30-45s or more iSteve
2006-02-07 12:56 ` Kay Sievers
2006-02-07 14:43 ` iSteve [this message]
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=43E8B22F.1010702@rulez.cz \
--to=isteve@rulez.cz \
--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).