HELP

Richard Couture rrc at myrddin.imat.com
Wed Feb 11 09:04:35 PST 1998


I am running Linux kernel 2.0.33 with the aic7xxx patch 5.0.5/3.2.2
with an Adaptec 2940U adapter.
I was running an older version of the driver and had problems, so I
got the newer driver to see if the problems would go away, but they
did not.
when I boot, dmesg reports the following:

[BEGIN DMESG RE:AIC]
  (scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 10/0
  (scsi0) Narrow Channel, SCSI ID=7, 16/255 SCBs
  (scsi0) BIOS enabled, IO Port 0xf800, IO Mem 0xffbef000, IRQ 11
  (scsi0) Downloading sequencer code... 406 instructions downloaded
  scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.0.5/3.2.2
       <Adaptec AHA-294X Ultra SCSI host adapter>
  scsi : 1 host.
  (scsi0:0:-1:-1) Scanning channel for devices.
  (scsi0:0:0:0) Synchronous at 10.0MHz, offset 15.
    Vendor: CONNER    Model: CFP1060S 1.05GB   Rev: 2035
    Type:   Direct-Access                      ANSI SCSI revision: 02
  Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
  (scsi0:0:1:0) Synchronous at 10.0MHz, offset 15.
    Vendor: CONNER    Model: CFP4207S  4.28GB  Rev: 1524
    Type:   Direct-Access                      ANSI SCSI revision: 02
  Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
  (scsi0:0:3:0) Synchronous at 6.67MHz, offset 15.
    Vendor: ARCHIVE   Model: Python 28388-XXX  Rev: 5.45
    Type:   Sequential-Access                  ANSI SCSI revision: 02
  Detected scsi tape st0 at scsi0, channel 0, id 3, lun 0
  scsi : detected 1 SCSI tape 2 SCSI disks total.
  SCSI device sda: hdwr sector= 512 bytes. Sectors= 2074880 [1013 MB]
  [1.0 GB]
  SCSI device sdb: hdwr sector= 512 bytes. Sectors= 8388608 [4096 MB]
  [4.1 GB]
[END DMESG RE:AIC]


When I back up the system I get the following errors:

[BEGIN ERROR REPORT]
  st0: Error with sense data: extra data not valid Current error
  st09:00: sense key Aborted Command
  Additional sense indicates Operator medium removal request
  st0: Error with sense data: extra data not valid Current error
  st09:00: sense key Not Ready
  Additional sense indicates Medium not present
  st0: Error with sense data: extra data not valid Current error
  st09:00: sense key Aborted Command
  Additional sense indicates Operator medium removal request
  (scsi0:0:0:0) Data overrun detected in Data-In phase, tag 14;
    Have seen Data Phase. Length=28672, NumSGs=5.
       sg[0] - Addr 0xb32000 : Length 4096
       sg[1] - Addr 0xb37000 : Length 12288
       sg[2] - Addr 0xb3b000 : Length 4096
       sg[3] - Addr 0xb3e000 : Length 4096
       sg[4] - Addr 0xb40000 : Length 4096
  scsi : aborting command due to timeout : pid 313876, scsi0, channel 0,
  id 0, lun 0 Read (6) 0d f0 70 5a 00 
  scsi : aborting command due to timeout : pid 313874, scsi0, channel 0,
  id 0, lun 0 Read (6) 0d f0 18 38 00 
  scsi : aborting command due to timeout : pid 313878, scsi0, channel 0,
  id 0, lun 0 Read (6) 16 84 e6 02 00 
  (scsi0:0:0:0) No active SCB for reconnecting target - Issuing BUS
  DEVICE RESET.
  (scsi0:0:0:0)       SAVED_TCL=0x0, ARG_1=0xe, SEQADDR=0x100
  (scsi0:0:0:0) Synchronous at 10.0MHz, offset 15.
  st0: Error with sense data: Current error st09:00: sense key Medium
  Error
  Additional sense indicates Sequential positioning error
  st0: Error with sense data: Current error st09:00: sense key Medium
  Error
  Additional sense indicates Sequential positioning error
  st0: Error with sense data: Current error st09:00: sense key Medium
  Error
  Additional sense indicates Sequential positioning error
  st0: Error with sense data: Current error st09:00: sense key Medium
  Error
  Additional sense indicates Sequential positioning error
[END ERROR REPORT]


Here is what /proc/scsi has to say:

[BEGIN /proc/scsi]
  Attached devices: 
  Host: scsi0 Channel: 00 Id: 00 Lun: 00
    Vendor: CONNER   Model: CFP1060S 1.05GB  Rev: 2035
    Type:   Direct-Access                    ANSI SCSI revision: 02
  Host: scsi0 Channel: 00 Id: 01 Lun: 00
    Vendor: CONNER   Model: CFP4207S  4.28GB Rev: 1524
    Type:   Direct-Access                    ANSI SCSI revision: 02
  Host: scsi0 Channel: 00 Id: 03 Lun: 00
    Vendor: ARCHIVE  Model: Python 28388-XXX Rev: 5.45
    Type:   Sequential-Access                ANSI SCSI revision: 02
[END /proc/scsi]


here is what /proc/scsi/0 has to say:

[BEGIN /proc/scsi/0]
  Adaptec AIC7xxx driver version: 5.0.5/3.2.2
  Compile Options:
    AIC7XXX_RESET_DELAY    : 15
    AIC7XXX_TAGGED_QUEUEING: Enabled (This is no longer an option)
      See AIC7XXX_TAGGED_QUEUEING_BY_DEVICE in the file
      drivers/scsi/aic7xxx.c to disable tagged queueing on 
      problematic devices.
    AIC7XXX_PAGE_ENABLE    : Enabled (This is no longer an option)
    AIC7XXX_PROC_STATS     : Disabled

  Adapter Configuration:
             SCSI Adapter: Adaptec AHA-294X Ultra SCSI host adapter
                             Narrow Controller
                  Base IO: 0xf800
           Base IO Memory: 0xffbef000
      BIOS Memory Address: 0x0
                           Enabled
                      IRQ: 11
                     SCBs: Active 0, Max Active 17,
                           Allocated 30, HW 16, Page 255
               Interrupts: 348417
     Extended Translation: Disabled
           SCSI Bus Reset: Enabled
  Disconnect Enable Flags: 0x00ff
   Tag Queue Enable Flags: 0x0003
  Ordered Queue Tag Flags: 0x0003
        BIOS Control Word: 0x1034
     Adapter Control Word: 0x0018
[END /proc/scsi/0]


In looking at the code in aic7xxx.c, I suspect that maybe I should
uncomment:

/* #define AIC7XXX_TAGGED_QUEUEING_BY_DEVICE */
then change:

adapter_tag_info_t aic7xxx_tag_info[] =
{
  {DEFAULT_TAG_COMMANDS},
  {{4, 0, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, -1, 4, 4, 4}},
  {DEFAULT_TAG_COMMANDS},
  {{-1, 16, 4, -1, 16, 4, 4, 4, 127, 4, 4, 4, 4, 4, 4, 4}}
};
to something like:

adapter_tag_info_t aic7xxx_tag_info[] =
{
  {{-1, 0, 0, -1, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0}},
  {{4, 0, 4, 4, 4, 4, 4, 4, 4, 4, 4, 4, -1, 4, 4, 4}},
  {DEFAULT_TAG_COMMANDS},
  {{-1, 16, 4, -1, 16, 4, 4, 4, 127, 4, 4, 4, 4, 4, 4, 4}}
};

but I hesitate to take such steps without knowing if I am on the right
track, and knowing what the ramifications might be, and knowing if
this a known problem with this particular configuration.

I am willing to change hardware if that might be a more elegant
solution, but I am not clear, from the info that I see, as to which
device is really causing the problems. 
Thank you for your patience in reading through all of this stuff, and
thank you in advance for your help and suggestions.



Richard
-- 
The CoffeeNet (R)               The greatest coffee AND the world (R)
744 Harrison Street at 3rd         --->>> FREE e-mail and <<<---
San Francisco, CA 94107-1235   --->>> FREE personal WEB page! <<<---
Voice: (415) 495-7447          e-mail: roastmaster at mail.coffeenet.net

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



More information about the aic7xxx mailing list