From owner-freebsd-questions  Thu Oct 12 00:49:28 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id AAA13452
          for questions-outgoing; Thu, 12 Oct 1995 00:49:28 -0700
Received: from smokey.ee.washington.edu (smokey.ee.washington.edu [128.95.75.8])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA13447
          ; Thu, 12 Oct 1995 00:49:26 -0700
Received: (from olsenc@localhost) by smokey.ee.washington.edu (8.6.11/8.6.9) id AAA00197; Thu, 12 Oct 1995 00:49:25 -0700
Date: Thu, 12 Oct 1995 00:49:25 -0700
From: Clint Olsen <olsenc@smokey.ee.washington.edu>
Message-Id: <199510120749.AAA00197@smokey.ee.washington.edu>
To: hardware@freebsd.org, questions@freebsd.org
Subject: SCSI_DELAY
Sender: owner-questions@freebsd.org
Precedence: bulk

It was suggested that I increase SCSI_DELAY.  As I suspected, it
didn't have any effect.  I changed it from 10 to 20 seconds.  I
doubt an eon would have any difference:

aic0 at 0x340-0x35f irq 11 on isa
aic0 waiting for scsi devices to settle
(aic0:1:0): "CDC 94171-9 0045" type 0 fixed SCSI 1
sd0(aic0:1:0): Direct-Access 312MB (640584 512 byte sectors)
(aic0:2:0): "unknown unknown ????" type 0 fixed SCSI 0

However, using scsi(8) commands does properly identify the second
disk.  Could the aic driver be at fault?

Thanks,

-Clint