From: Mike Anderson <andmike@us.ibm.com>
To: "Thomas Langås" <tlan@stud.ntnu.no>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Weird Qlogic 2200 FC HBA / CNSI G7324 problem
Date: Fri, 12 Jul 2002 09:16:03 -0700 [thread overview]
Message-ID: <20020712091603.A10141@beaverton.ibm.com> (raw)
In-Reply-To: <20020712111842.A12686@stud.ntnu.no>; from tlan@stud.ntnu.no on Fri, Jul 12, 2002 at 11:18:42AM +0200
Thomas Langås [tlan@stud.ntnu.no] wrote:
> Thomas Langås:
> > Just a quick update; doing the following works:
> > echo "scsi add-single-device 1 0 0 1" > /proc/scsi/scsi
> > Which indicates that's the detection code somewhere which
> > isn't like it should?
>
>
> And, to keep on replying to myself; the redhat kernel didn't
> have "Probe all SCSI LUNs" enabled, adding that and it finds
> everything like it should. Any reason why it doesn't without
> this option?
With this config option not selected non zero luns will not be probed. You
can also pass max_scsi_luns on the command line without re-compiling your
kernel. Someone from RedHat would be better to comment on the default
selection, but as you will see if you review the archive of this mail list
there have been passed issues of probing non-zero luns on older devices
not included in the scsi devicelist, so defaulting to off is possibly a
conservative selection.
-Mike
--
Michael Anderson
andmike@us.ibm.com
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2002-07-12 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 23:08 Weird Qlogic 2200 FC HBA / CNSI G7324 problem Thomas Langås
[not found] ` <20020711164141.B8468@beaverton.ibm.com>
2002-07-12 0:45 ` Thomas Langås
2002-07-12 8:23 ` Thomas Langås
2002-07-12 9:18 ` Thomas Langås
2002-07-12 16:16 ` Mike Anderson [this message]
2002-07-12 23:13 ` Thomas Langås
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=20020712091603.A10141@beaverton.ibm.com \
--to=andmike@us.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tlan@stud.ntnu.no \
/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