Date: Mon, 17 Jan 2000 17:21:06 +0000 From: Dave Rynne <dave@esat.net> To: freebsd-scsi@freebsd.org Subject: Problems with Mylex eXtremeRAID 1100 (DAC 1164) Message-ID: <E12AFpy-0003uQ-00@lucidity.esat.net>
next in thread | raw e-mail | index | archive | help
Hi... Am having probs with a Mylex eXtremeRAID 1100 (DAC1164) under both 3.4-RELEASE & 4.0-CURRENT. Card gets detected fine when no disks are attached but fails to detect card properly when disks are attached (and takes a few mins to even boot). Have also tried Linux & NT on the same box and both install fine so it doesn't appear to be a hardware problem (termination, etc..). Relevant chunks from bootverbose (4.0-20000112-CURRENT): Without disks attached: mlx0: <Mylex version 5 RAID interface> port 0xdc80-0xdcff mem 0xec000000-0xeffff fff,0xf7fffc00-0xf7fffc7f irq 14 at device 8.0 on pci3 mlx0: DAC1164PVX, 2 channels, firmware 5.07-0-79, 64MB RAM mlx0: Hardware ID 0x03020220 mlx0: Firmware ID 0x304f0705 mlx0: Configured/Actual channels 2/2 mlx0: Max Targets 16 mlx0: Max Tags 236 mlx0: Max System Drives 32 mlx0: Max Arms 8 mlx0: Max Spans 4 mlx0: DRAM/cache/flash/NVRAM size 67108864/64905216/1048576/32768 mlx0: DRAM type 10 mlx0: Clock Speed 40ns mlx0: Hardware Speed 360ns mlx0: Max Commands 128 mlx0: Max SG Entries 33 mlx0: Max DP 472 mlx0: Max IOD 1024 mlx0: Max Comb 256 mlx0: Latency 12s mlx0: SCSI Timeout 18s mlx0: Min Free Lines 72 mlx0: Rate Constant 50 mlx0: MAXBLK 128 mlx0: Blocking Factor 1 sectors mlx0: Cache Line Size 16 blocks mlx0: SCSI Capability 40MHz, 16 bit mlx0: Firmware Build Number 0 mlx0: Fault Management Type 0 mlx0: Features 0 mlxd0: <Mylex System Drive> on mlx0 mlxd0: 0MB (0 sectors) RAID 7 (offline) mlxd1: <Mylex System Drive> on mlx0 mlxd1: 0MB (0 sectors) RAID 7 (offline) With disks attached: mlx0: <Mylex version 5 RAID interface> port 0xdc80-0xdcff mem 0xec000000-0xeffff fff,0xf7fffc00-0xf7fffc7f irq 14 at device 8.0 on pci3 mlx0: DAC model 0x80, 0 channel, firmware 0.00--0, 0MB RAM mlx0: Hardware ID 0xc1343280 mlx0: Firmware ID 0x00000000 mlx0: Configured/Actual channels 0/0 mlx0: Max Targets 0 mlx0: Max Tags 0 mlx0: Max System Drives 0 mlx0: Max Arms 0 mlx0: Max Spans 0 mlx0: DRAM/cache/flash/NVRAM size 0/0/0/0 mlx0: DRAM type 0 mlx0: Clock Speed 0ns mlx0: Hardware Speed 0ns mlx0: Max Commands 0 mlx0: Max SG Entries 0 mlx0: Max DP 0 mlx0: Max IOD 0 mlx0: Max Comb 0 mlx0: Latency 0s mlx0: SCSI Timeout 0s mlx0: Min Free Lines 0 mlx0: Rate Constant 0 mlx0: MAXBLK 0 mlx0: Blocking Factor 0 sectors mlx0: Cache Line Size 0 blocks mlx0: SCSI Capability 10MHz, 8 bit mlx0: Firmware Build Number 0 mlx0: Fault Management Type 0 mlx0: Features 0 mlx0: *** WARNING *** This firmware revision is not recommended mlx0: *** WARNING *** Use revision 5.07 or later mlx0: error fetching drive status mlx0: done event for nonbusy slot 255 mlx0: done event for nonbusy slot 255 mlx0: done event for nonbusy slot 255 mlx0: done event for nonbusy slot 255 mlx0: done event for nonbusy slot 0 Have been seeing this behaviour with various 4.0 snapshots since late Novemeber. Box also has both ahc and amr controllers and is booting off the ahc. Any ideas ? Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E12AFpy-0003uQ-00>