Date: Fri, 9 Oct 1998 11:08:45 -0500 (CDT) From: Greg Whalin <gwhalin@numerix.com> To: AIC7xxx List <aic7xxx@FreeBSD.ORG>, Doug Ledford <dledford@dialnet.net> Subject: Still a no go with 5.1.1 and my CMD RAID card Message-ID: <Pine.LNX.4.02.9810091059270.4772-100000@co.numerix.com>
next in thread | raw e-mail | index | archive | help
Here is some output from the last working pre-release that I tried (pre7)
aic7xxx: Warning - detected auto-termination on controller:
aic7xxx: <Adaptec AHA-294X Ultra SCSI host adapter> at PCI 17/0
aic7xxx: Please verify driver detected settings are correct.
aic7xxx: If not, then please properly set the device termination
aic7xxx: in the Adaptec SCSI BIOS by hitting CTRL-A when prompted
aic7xxx: during machine bootup.
aic7xxx: Cables present (Int-50 NO, Int-68 YES, Ext-68 NO)
(scsi0) <Adaptec AHA-294X Ultra SCSI host adapter> found at PCI 17/0
(scsi0) Wide Channel, SCSI ID=7, 16/255 SCBs
(scsi0) Downloading sequencer code... 419 instructions downloaded
scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.0pre7/3.2.4
<Adaptec AHA-294X Ultra SCSI host adapter>
scsi : 1 host.
Vendor: CMD TECH Model: CRD-5440 Rev: C0-1
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
scsi : detected 1 SCSI disk total.
(scsi0:0:0:0) Synchronous at 40.0 Mbyte/sec, offset 8.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 8394752 [4099 MB] [4.1GB]
and ... /proc/scsi/aic7xxx/0
Adaptec AIC7xxx driver version: 5.1.0pre7/3.2.4
Compile Options:
AIC7XXX_RESET_DELAY : 5
AIC7XXX_TAGGED_QUEUEING: Adapter Support Enabled
Check below to see which
devices use tagged queueing
AIC7XXX_PAGE_ENABLE : Enabled (This is no longer an option)
AIC7XXX_PROC_STATS : Enabled
Adapter Configuration:
SCSI Adapter: Adaptec AHA-294X Ultra SCSI host adapter
Ultra Wide Controller
PCI MMAPed I/O Base: 0xffbef000
Adaptec SCSI BIOS: Enabled
IRQ: 10
SCBs: Active 0, Max Active 4,
Allocated 45, HW 16, Page 255
Interrupts: 2712
BIOS Control Word: 0x18b6
Adapter Control Word: 0x007f
Extended Translation: Enabled
Disconnect Enable Flags: 0xffff
Ultra Enable Flags: 0xffff
Tag Queue Enable Flags: 0x0001
Ordered Queue Tag Flags: 0x0001
Default Tag Queue Depth: 32
Tagged Queue By Device array for aic7xxx host instance 0:
{0,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
Actual queue depth per device for aic7xxx host instance 0:
{32,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
Statistics:
(scsi0:0:0:0)
Device using Wide/Sync transfers at
40.0 MByte/sec, offset 8
Total transfers 2657 (1986 read;671 written)
blks(512) rd=11381; blks(512) wr=2488
< 512 512-1K 1-2K 2-4K 4-8K 8-16K 16-32K 32-64K 64-128K >128K
Reads: 0 1 1364 33 265 312 6 4 1 0
Writes: 0 0 529 115 13 5 5 4 0 0
Here is the output when I reboot with 5.1.1 with the boot options ...
aic7xxx=panic_on_abort,verbose:0x1ffff
It gives the exact same output. It basically just hangs telling me that
it couldn't mount the root partition (obviously because the RAID
controller was not found).
This worked up until pre4 (I think) and then stopped working. After I
reported this, it was fixed in pre5 or6 and worked at least until pre7.
Stopped working around pre10 or 11 I think, and still does not work. It
basically just does not detect the RAID controller. This is a pain now
that 5.1.1 is being distributed in all new kernel releases. This meanse
that I will have to back port to get this system to boot in the event of a
kernel upgrade.
Thoughts??
Thanks,
Greg
--------------------
Greg Whalin
gwhalin@numerix.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.02.9810091059270.4772-100000>