From owner-aic7xxx  Sun Sep  7 19:17:19 1997
Return-Path: <owner-aic7xxx>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA26965
          for aic7xxx-outgoing; Sun, 7 Sep 1997 19:17:19 -0700 (PDT)
Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26960
          for <aic7xxx@FreeBSD.ORG>; Sun, 7 Sep 1997 19:17:16 -0700 (PDT)
Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id UAA05232; Sun, 7 Sep 1997 20:43:01 -0500 (CDT)
Message-Id: <199709080143.UAA05232@iworks.InterWorks.org>
Date: Sun, 7 Sep 1997 20:43:01 -0500 (CDT)
From: "Daniel M. Eischen" <deischen@iworks.InterWorks.org>
To: aic7xxx@FreeBSD.ORG, shirsch@ibm.net
Subject: Re: Adaptec driver broken on 2740T
Sender: owner-aic7xxx@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


> I have bad news.  The adaptec aic7xxx driver in Linux 2.0.31-pre-9 is
> broken for my EISA bus 2740T controller.  It seems to scan the drives on
> bus A properly, then goes into an endless loop of kernel paging errors and
> scsi resets when attempting to scan bus B (which has nothing on it, BTW).
> 
> I reverted back to the older driver to test other aspects of pre-9 (looks
> fine so far..).
>
> You certainly don't want this driver included as-is in the final 2.0.31
> release, though.

Well, there are too many bugs with the previous driver, so unless
someone with a 274x can figure it out ;-) 

Doug Ledford found one bug that may be causing problems.  It is in
aic7xxx_register where we do this:

  for (i = 0; i <= NUMBER(p->device_status); i++)
  {
    p->device_status[i].commands_sent = 0;
    p->device_status[i].flags = 0;
    p->device_status[i].active_cmds = 0;
    p->device_status[i].last_reset = 0;
  }

Change the first line to this:

  for (i = 0; i < NUMBER(p->device_status); i++)

It's on or abouts like 5011 in aic7xxx.c.

Dan Eischen
deischen@iworks.InterWorks.org