From mboxrd@z Thu Jan  1 00:00:00 1970
From: iSteve <isteve@rulez.cz>
Date: Tue, 07 Feb 2006 14:43:59 +0000
Subject: Re: UDev startup 30-45s or more
Message-Id: <43E8B22F.1010702@rulez.cz>
MIME-Version: 1
Content-Type: multipart/mixed; boundary="------------030007000300030109090808"
List-Id: <linux-hotplug.vger.kernel.org>
References: <43E896DB.2080506@rulez.cz>
In-Reply-To: <43E896DB.2080506@rulez.cz>
To: linux-hotplug@vger.kernel.org

This is a multi-part message in MIME format.
--------------030007000300030109090808
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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)

--------------030007000300030109090808
Content-Type: text/plain;
 name="pcmcia.rules"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="pcmcia.rules"

# 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"

--------------030007000300030109090808--


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel