From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
The aic7xxx driver fails while configuring the SCSI RAID box from Winchester
Systems. The driver seems to configure the adapter fine, but when it is probing
the SCSI LUNs the driver goes into an infinite loop spewing firmware dump
information. See attachment.
This does not happen with the aic7xxx_old driver. It also does not happen with
the taroon-a4 kernel, which had the older version of the aic7xxx driver.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot with Winsys raid box attached
Works: 6.2.8, and aic7xxx_old
Created attachment 94476 [details]
This looks like a bug in the box firmware to me. It reports scsi level 4 but
doesn't properly support high lun numbers. I'm not positive that the extended
lun support is optional in scsi level 4. Adding Justin to the cc list so he can
Justin did comment on this in mail to me. I thought I put this in the bugzilla,
but I guess not. Sorry.
> The rev 6.2.36 driver fails to configure the Winchester RAID box. The
> rev 6.2.8 driver, and aic7xxx_old work.
Have you limted the number of LUNs exported by either the 6.2.8 driver
or the aic7xxx_old driver to something <= 32? It looks like this particular
device cannot handle probing of luns > 32 - it ignores the high bit and
doesn't return it during reselection causing the driver to abort the command.
Perhaps there was a quirk entry for this device that prevented the high
scan? Anyway, any device claiming SPC2 compliance (ANSI Rev 04) should
allow the high scan, so this guy looks broken.
I am working with Winchester to get this fixed.
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.