no_reset option (was: 5.1.6 failure too..)

[Dirk Lutzebaeck]

 > Yes, I have an idea.  Try the no_reset option to the driver.  If that
 > solves your problem, then one of two things is true.  Either the bus
 > reset at driver init time isn't happening properly (even if the driver
 > thinks it is, which is one problem I had before) or the device doesn't
 > like the bus reset (which isn't a problem I've seen with HP DATs in the
 > past so I doubt it).
 > 
 > The fix to your problem may be as simple as going into the
 > aic7xxx_detect() code around line 9066 and right after the call to
 > aic7xxx_chip_reset() adding an mdelay(250) or some such wait period.  My
 > untested theory is that certain aic7xxx chips need a delay after the
 > chip reset before they will actually output anything on the SCSI bus
 > pins (more than just what running through the rest of the code provides
 > anyway).  This is especially true with 7890 chips, and you can see that
 > the aic7xxx_register() function already has a delay in it specifically
 > for all ultra2 chipsets, but we may need a general delay to catch all of
 > the chipsets that need it.  The other half of my theory is that freebsd

My Scorpion Seagate DAT also isn't recognized after a driver bus reset
but answers only when using the no_reset option while booting.  This
is now on Linux 2.0.36 patched to 5.1.6 on an ASUS P2B-DS U2W/7890. I
have tried the mdelay patch with 250 and 500 but the drive isn't
recognized either.

Dirk


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