From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: scsi.agent trouble: load more than module per TYPE
Date: Wed, 18 Jan 2006 21:05:28 +0000 [thread overview]
Message-ID: <20060118210528.GA22783@us.ibm.com> (raw)
In-Reply-To: <20060118182519.4c7bd4b5@lounge.fly.net>
On Wed, Jan 18, 2006 at 09:16:50PM +0100, Marco d'Itri wrote:
> On Jan 18, Patrick Mansfield <patmans@us.ibm.com> wrote:
>
> > IMHO, sg should still be loaded for all scsi devices, especially for
> > ones that have an odd (such as enclousre or raid) or unknown type. Looks
> > like only SUSE does it this way.
> Nobody ever opened a bug suggesting to do it differently, so I did not
> bother changing the rules used by Debian.
If you don't want to always load sg, at least load sg if no other driver
is loaded for the scsi device. That might even be better than always
loading it (sort of force SG_IO users to use /dev/sd ...).
I don't know why sr_mod is loaded for type 3 (processor), unless you have
patched sr.c sr_probe(), sr only attaches to 5 (TYPE_ROM) and 4
(TYPE_WORM).
So use (for debian at least, not tested at all):
SUBSYSTEM="scsi_device", SYSFS{type}!="[0|1|4|5|7|14]", RUN+="/sbin/modprobe sg"
-- Patrick Mansfield
-------------------------------------------------------
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-18 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 17:25 scsi.agent trouble: load more than module per TYPE Michele Barbiero
2006-01-18 19:16 ` Marco d'Itri
2006-01-18 19:45 ` Michele Barbiero
2006-01-18 19:49 ` Marco d'Itri
2006-01-18 20:09 ` Patrick Mansfield
2006-01-18 20:16 ` Marco d'Itri
2006-01-18 21:05 ` Patrick Mansfield [this message]
2006-01-19 3:58 ` Andrey Borzenkov
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=20060118210528.GA22783@us.ibm.com \
--to=patmans@us.ibm.com \
--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).