AIC7xxx in 2.0.34 - Failing to detect my SCSI devices.

[Greg Patterson]

-----BEGIN PGP SIGNED MESSAGE-----

Okay,

The new SCSI code changes in 2.0.34 is giving me problems. I have been
reliably using the aic7xxx driver with my system for ages without anything
noteworthy to report.  

Since installing 2.0.34, while booting up, the point where the driver is
"Scanning channel for devices." is randomly not finding one of my devices.
I have a Quantum 1gb Fireball as my root (/) & boot drive and a Plextor
4x/12x CD-R both on my AHA-2940UW. 

In the past 5-8 reboots since installing 2.0.34, I've seen the driver fail
to detect the Quantum boot drive at least 3 or 4 times. I figured it might
help to increase CONFIG_AIC7XXX_RESET_DELAY from 7 to 12 but it is still
not reliably detecting both devices. In all cases, it has been a warm
reboot and these devices should have been ready or spinning (quantum). 

This time around my Quantum showed up but my Plextor CD-R did not:

aic7xxx: Warning - detected auto-termination on controller:
aic7xxx: <Adaptec AHA-294X Ultra SCSI host adapter> at PCI 12/0
aic7xxx: Please verify driver detected settings are correct.
aic7xxx: If not, then please properly set the device termination
aic7xxx: in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
aic7xxx: during machine bootup.
aic7xxx: Cables present (Int-50 YES, Int-68 NO, Ext-68 NO)
aic7xxx: Termination (Low ON, High ON)
(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 12/0
(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
(scsi0) BIOS enabled, IO Port 0xd800, IRQ 11
(scsi0) IO Memory at 0xf8000000, MMAP Memory at 0x880d000
(scsi0) Resetting channel
(scsi0) Downloading sequencer code... 406 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.0.14/3.2.4
       <Adaptec AHA-294X Ultra SCSI host adapter>
scsi : 1 host.
(scsi0:0:-1:-1) Scanning channel for devices.
(scsi0:0:6:0) Refusing WIDE negotiation; using 8 bit transfers.
(scsi0:0:6:0) Synchronous at 10.0MHz, offset 8.
  Vendor: QUANTUM   Model: FIREBALL1080S     Rev: 1Q08
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 6, lun 0
scsi : detected 1 SCSI disk total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 2134305 [1042 MB] [1.0
GB]

It should have showed (scsi0:0:4:0):

  Vendor: PLEXTOR   Model: CD-R   PX-R412C   Rev: 1.03
  Type:   CD-ROM                             ANSI SCSI revision: 02

before the Quantum.....

I am using LOADLIN with no fancy parameters for the aic7xxx driver what so
ever (eg. no_reset). In this case I dont really care about the PLEXTOR not
cominging up but if the power goes out and my system goes out and comes
back up again, chances are it will be the Quantum that doesn't get
detected next time around thus putting the system in a useless state. 

Please let me know if there is anything I can do to help debug this... I
would have liked to display the errors I get when the Quantum doesn't get
detected but I'll need to write that down by hand since I cant get into
the system if that drive doesn't come up.

Also, I have tired the most recently available aic7xxx update (5.0.18 + a
.19 patch) and after 30 reboots with this code while trying various LILO
boot parameters (actually LOADLIN), nada, no CD-R or drive. I've since
gone back to 2.0.33.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: PGP Signed with PineSign 2.0

iQCVAwUBNXwAx/AH0eZN+dr9AQHX+AQAlgE99CUsZOBZbMunYAODHzBxoDQn5j8h
s+8RmyeFMLY69+7W6GfIa5FERHixONg59r09Ti1IItSnAjdVDqdMOqF+D42Yc0v2
an+W5xhGcj1hIA7/c4vEFOSMQWnR5H5TNjy80D8oBgkMXLSF3NAtxjCWHtFzq7lT
HjRWBKrQ+Og=
=ekOj
-----END PGP SIGNATURE-----
 
================================================================
|    Greg Patterson      | EMAIL: gomer at gomer.mlink.net        |
|                        |        gomer at mlink.net              |
| Move over Microsoft,   | IRC:   Wizird (EFNET)               |
| Linux is here to stay. | WWW:   http://gomer.mlink.net/~root |
================================================================


To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message