From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: sd_mod load is delayed.
Date: Sun, 29 Jan 2006 10:12:18 +0000 [thread overview]
Message-ID: <200601291312.19411.arvidjaar@mail.ru> (raw)
In-Reply-To: <cfb54190601290129x68c9885fybc0ac07aa1502f9f@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 29 January 2006 12:29, Hai Zaar wrote:
> Hi!
>
> I'm using 2.6.15 + udev 081 + udev rules from here:
> http://ftp.jg555.com/udev/udev-cross-lfs.tar.bz2 Relevant modprobe rules
> are: # hotplug
> ENV{MODALIAS}="?*", RUN+="/sbin/modprobe $env{MODALIAS}"
>
> # scsi
> SUBSYSTEM="scsi_device", ACTION="add", SYSFS{device/type}="1",
> SYSFS{device/vendor}="On[sS]tream", RUN+="/sbin/modprobe osst"
> SUBSYSTEM="scsi_device", ACTION="add", SYSFS{device/type}="1",
> RUN+="/sbin/modprobe st"
> SUBSYSTEM="scsi_device", ACTION="add", SYSFS{device/type}="[45]",
> RUN+="/sbin/modprobe sr_mod"
> SUBSYSTEM="scsi_device", ACTION="add", RUN+="/sbin/modprobe sg"
>
> Those rules do not handle sd_mod loading, so I've added the following
> line from SUSE rules:
> SUBSYSTEM="scsi_device", ACTION="add",
> SYSFS{device/type}="0|7|14", RUN+="/sbin/modprobe sd_mod"
>
> I have two storage controllers in my machine:
> 1. Intel SATA controller, handled by ata_piix driver.
> 2. LSI logic SCSI controller handled by mptlinux driver.
>
> The situation:
> During initramfs stage, if I trigger event only for SATA controller,
> then after just 1 second lib_ata and ata_piix modules are loaded
> together with sd_mod and friends, and /proc/partitions is populated.
> So just after 1-2 seconds I'm able boot from SATA.
>
> When LSI logic event is triggered - mptlinux module is loaded and
> spends about half a minute to scan the bus.
>
> The problems with, that when I trigger events both for SATA and LSI
> logic (like trigger_all_events function does), sd_mod is not get
> loaded until _both_ SATA and LSI finish to initialize.
> Why sd_mod is not get loaded just right after ata_piix has finished?
>
As far as I can tell, SCSI subsystem is using scan mutex; so only one HBA can
do scanning at a time. Or so it appears. May be LSI is the frst one to kick
in.
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD3JUDR6LMutpd94wRAskLAJ9zBL3CHW4ovt4vxApZp2cVsiuQRwCfdpRU
i+VgPRPUSNiTCOkoCyfrKoM=/SSI
-----END PGP SIGNATURE-----
-------------------------------------------------------
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\x103432&bid#0486&dat\x121642
_______________________________________________
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
next prev parent reply other threads:[~2006-01-29 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 9:29 sd_mod load is delayed Hai Zaar
2006-01-29 10:12 ` Andrey Borzenkov [this message]
2006-01-29 10:39 ` Andrey Borzenkov
2006-01-29 11:18 ` Hai Zaar
2006-01-29 12:24 ` Andrey Borzenkov
2006-01-29 12:40 ` Hai Zaar
2006-01-29 14:55 ` Kay Sievers
2006-01-29 15:19 ` Hai Zaar
2006-01-30 14:43 ` Hai Zaar
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=200601291312.19411.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).