Trouble with aic7902 under linux-2.4.21*

[Juergen Rose]

Hi Justin and everybody else in this list,

I have a TYAN  S2665 Thunder i75505 mainboard with aic7902 controller.  
I tested several new kernels:
    linux-2.4.21
    linux-2.4.21-ac4
    linux-2.4.22p2
    linux-2.4.22p3
    linux-2.4.22p5
I think that at least the last to kernel includes the most current 
aic79xx driver (1.3.10). The controller should have transfer rates of 
320 MBytes/sec on both busses. In the adaptec bios the controller is 
configured, to have these rates. But when I am booting linux, I get the
following:

SCSI subsystem driver Revision: 1.00
scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.10
        <Adaptec AIC7902 Ultra320 SCSI adapter>
        aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 
512 SCBs

scsi1 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.3.10
        <Adaptec AIC7902 Ultra320 SCSI adapter>
        aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 67-100Mhz, 
512 SCBs

blk: queue f793ee98, I/O limit 4095Mb (mask 0xffffffff)
(scsi1:A:1): 40.000MB/s transfers (20.000MHz, 16bit)
(scsi1:A:2): 40.000MB/s transfers (20.000MHz, 16bit)
(scsi0:A:3): 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit)
(scsi0:A:4): 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit)

I can work with both busses, but the bus1 is also with bonnie++ at least
50 % slower than bus0:

             ---Sequential-Output-----------  --Sequential Input--
       Size  Per Char-  --Block--  -Rewrite-   Per Char-  --Block--
Machine  GB  K/sec %CP  K/sec %CP  K/sec %CP   K/sec %CP  K/sec %CP
bornholm  7  28034  97  50599  24  28010   9   30579  88  58413  11
/dev/scsi/host0/bus0/target3/lun0/part2
bornholm  7  27257  94  53227  25  29197  10   31238  90  56044   9
/dev/scsi/host0/bus0/target4/lun0/part2
bornholm  7  19730  69  36062  17  17463   5   29496  84  35135   5
/dev/scsi/host1/bus0/target1/lun0/part2
bornholm  7   19775 68  36764  17  17339   5   30150  86  35168   5
/dev/scsi/host1/bus0/target2/lun0/part2

Do you mean that the driver is responsible, or is it a hardware problem?
I would appreciate  very much  any hint.

     With best regards
             Juergen