From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: "chen, xiangping" <chen_xiangping@emc.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A bug in the new aic7xxx.o driver in kernel 2.4.7
Date: Fri, 24 Aug 2001 17:22:07 -0600 [thread overview]
Message-ID: <200108242322.f7ONM7Y53087@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "Tue, 07 Aug 2001 16:21:09 EDT." <276737EB1EC5D311AB950090273BEFDD043BC557@elway.lss.emc.com>
>It fails to detected all the external scsi devices, and communicate with
>devices when there is a gap between lun numbers. If there is a gap, it
>omits devices from the absent lun number to the next 2 power # lun number,
>and I/O error after that.
>For example, if device /dev/scsi/host1/bus0/target1/lun7 is taken out
>from the system, the aic7xxx driver fails to detect disks from
>/dev/scsi/host1/bus0/target1/lun8
>to /dev/scsi/host1/bus0/target1/lun31, in stead jumps to ..../lun32,
>and fails to talk to the device ever since.
>
>Old aic7xxx driver is OK.
You'll need to enable additional SCSI logging to determine what is going
on here. The aic7xxx driver doesn't care about lun numbers really, and
doesn't have any code to "willy-nilly" reject some subset of luns just
because one was not probed. What I really need to see is what error
code was returned by the aic7xxx driver when the attempt to probe the
"not found" lun occurs. You should be able to instrument the non
"hardcoded" section of drivers/scsi/scsi_scan.c:scan_scsis() to get
this information.
--
Justin
prev parent reply other threads:[~2001-08-24 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-07 20:21 chen, xiangping
2001-08-24 23:22 ` Justin T. Gibbs [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=200108242322.f7ONM7Y53087@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=chen_xiangping@emc.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®