From owner-freebsd-scsi Mon Jan 17 9:21:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lucidity.esat.net (lucidity.esat.net [193.120.10.32]) by hub.freebsd.org (Postfix) with ESMTP id CE77014C12 for ; Mon, 17 Jan 2000 09:21:07 -0800 (PST) (envelope-from dave@esat.net) Received: from localhost ([127.0.0.1] helo=esat.net ident=dave) by lucidity.esat.net with esmtp (Exim 3.13 #1) id 12AFpy-0003uQ-00 for freebsd-scsi@freebsd.org; Mon, 17 Jan 2000 17:21:06 +0000 X-Mailer: exmh version 2.0.3 To: freebsd-scsi@freebsd.org Subject: Problems with Mylex eXtremeRAID 1100 (DAC 1164) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 17:21:06 +0000 From: Dave Rynne Message-Id: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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: 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: on mlx0 mlxd0: 0MB (0 sectors) RAID 7 (offline) mlxd1: on mlx0 mlxd1: 0MB (0 sectors) RAID 7 (offline) With disks attached: mlx0: 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 From owner-freebsd-scsi Mon Jan 17 16:21:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 9727814EF1 for ; Mon, 17 Jan 2000 16:21:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA02122; Mon, 17 Jan 2000 16:23:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001180023.QAA02122@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dave Rynne Cc: freebsd-scsi@freebsd.org Subject: Re: Problems with Mylex eXtremeRAID 1100 (DAC 1164) In-reply-to: Your message of "Mon, 17 Jan 2000 17:21:06 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jan 2000 16:23:01 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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..). It looks like the controller's being left in a state that the driver doesn't like; commands are completing but return garbage. > Relevant chunks from bootverbose (4.0-20000112-CURRENT): > > Without disks attached: > mlx0: 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 ... > With disks attached: > mlx0: 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 The ENQUIRY2 command has completed OK, but the data it has returned is complete nonsense. > Have been seeing this behaviour with various 4.0 snapshots since > late Novemeber. Was there ever a time that it worked for you? > Box also has both ahc and amr controllers and is booting off the > ahc. > > Any ideas ? Not yet, but I'm hamstrung right now in that -current is hopelessly unstable, and won't even boot SMP on my test system, so I'm unable to do any work on these drivers. As soon as I can, I will, and I'll try to reproduce your problem. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jan 17 17:12:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from lucidity.esat.net (lucidity.esat.net [193.120.10.32]) by hub.freebsd.org (Postfix) with ESMTP id 178DE150CF; Mon, 17 Jan 2000 17:12:03 -0800 (PST) (envelope-from dave@esat.net) Received: from localhost ([127.0.0.1] helo=esat.net ident=dave) by lucidity.esat.net with esmtp (Exim 3.13 #1) id 12ANBe-0004fB-00; Tue, 18 Jan 2000 01:11:58 +0000 To: Mike Smith Cc: Dave Rynne , freebsd-scsi@freebsd.org Subject: Re: Problems with Mylex eXtremeRAID 1100 (DAC 1164) In-Reply-To: Your message of "Mon, 17 Jan 2000 16:23:01 PST." <200001180023.QAA02122@mass.cdrom.com> Date: Tue, 18 Jan 2000 01:11:58 +0000 From: Dave Rynne Message-Id: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Have been seeing this behaviour with various 4.0 snapshots since > > late Novemeber. > > Was there ever a time that it worked for you? No, but I've never spent too much time trying to get it working - tried every so often but just figured the driver was still very much in development and would stabilise shortly. Now, I'm about to add a lot more disk to an existing box and was (still am :) hoping to convert it from Linux to FreeBSD in the process. > > > Box also has both ahc and amr controllers and is booting off the > > ahc. > > > > Any ideas ? > > Not yet, but I'm hamstrung right now in that -current is hopelessly > unstable, and won't even boot SMP on my test system, so I'm unable to do > any work on these drivers. As soon as I can, I will, and I'll try to > reproduce your problem. Let me know if you need me to do any testing... > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jan 18 3:42:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 78B9E14F1E for ; Tue, 18 Jan 2000 03:42:19 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id MAA59180 for ; Tue, 18 Jan 2000 12:42:15 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Tue, 18 Jan 2000 12:42:15 +0100 (CET) From: Trond Endrestol To: FreeBSD SCSI Subject: Problems accessing the tapestreamer, possible kernel bug Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, After having cvsup'ed to 3.4-stable, recompiling and reinstalling, I can no longer access the tapestreamer. I tried booting with the old 3.3-GENERIC kernel and everything works OK with that kernel. There's no problem with mt or tar, it's kernel related. Our tapestreamer is identified at reboot as sa0: Removable Sequential Access SCSI-2 device sa0: 7.812MB/s transfers (7.812MHz, offset 15) And it's made by Seagate. Trying to use mt status with a valid tape inserted results in both LEDs turned on (both the yellow and the green) and mt hangs. The only way to kill mt is to hit the eject button on the streamer. Below is the current dmesg output and the current kernel configuration file. The kernel configuration file was based on the GENERIC file from 3.3-release and I see no functional difference between the current kernel configuration file and the current GENERIC file. Perhaps there's some problem with the sa driver. Does someone have a clue? BTW, do I need the pass0 device? -- Here's the complete dmesg output: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-STABLE #0: Wed Jan 12 16:30:34 CET 2000 root@ramstind.gtf.ol.no:/usr/src/sys/compile/RAMSTIND Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451025054 Hz CPU: Pentium III (451.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff> real memory = 134217728 (131072K bytes) avail memory = 127696896 (124704K bytes) Preloaded elf kernel "kernel" at 0xc02bd000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02bd09c. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 chip3: rev 0x02 on pci0.7.3 xl0: <3Com 3c900B-COMBO Etherlink XL> rev 0x04 int a irq 9 on pci0.11.0 xl0: Ethernet address: 00:50:da:3b:23:2d xl0: autonegotiation not supported ahc0: rev 0x00 int a irq 5 on pci0.13.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0x7a int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, dma, iordis acd0: drive speed 0 - 8250KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 vga0 at 0x3c0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 7.812MB/s transfers (7.812MHz, offset 15) da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) changing root device to da0s1a -- And here's the current kernel configuration file: # # RAMSTIND -- Konfigurasjonsfil for ramstind.gtf.ol.no # trond, 1999-11-23, basert på # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.freebsd.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.ORG/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.143.2.22 1999/09/14 22:53:30 jkh Exp $ machine "i386" #cpu "I386_CPU" #cpu "I486_CPU" #cpu "I586_CPU" cpu "I686_CPU" ident RAMSTIND maxusers 32 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores config kernel root on da0 # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 #controller pnp0 # PnP support for ISA #controller eisa0 controller pci0 # Floppy drives controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 #disk fd1 at fdc0 drive 1 # IDE controller and disks options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 # ATAPI devices options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM #device wfd0 #IDE Floppy (e.g. LS-120) # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc) is # sufficient for any number of installed devices. #controller ncr0 # NCR/Symbios Logic #controller ahb0 # EISA AHA1742 family controller ahc0 # AHA2940 and onboard AIC7xxx devices #controller amd0 # AMD 53C974 (Teckram DC-390(T)) #controller isp0 # Qlogic family #controller dpt0 # DPT Smartcache - See LINT for options! #controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? #controller aha0 at isa? port ? cam irq ? # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) #device cd0 # CD device pass0 # Passthrough device (direct SCSI) # Proprietary or custom CD-ROM Interfaces #device wt0 at isa? port 0x300 bio irq 5 drq 1 #device mcd0 at isa? port 0x300 bio irq 10 #device matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at isa? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? # Serial (COM) ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 at ppbus? # Printer device plip0 at ppbus? # TCP/IP over parallel device ppi0 at ppbus? # Parallel port interface device #controller vpo0 at ppbus? # Requires scbus and da0 # PCI Ethernet NICs. #device al0 # ADMtek AL981 (``Comet'') #device ax0 # ASIX AX88140A #device de0 # DEC/Intel DC21x4x (``Tulip'') #device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device mx0 # Macronix 98713/98715/98725 (``PMAC'') #device pn0 # Lite-On 82c168/82c169 (``PNIC'') #device rl0 # RealTek 8129/8139 #device sf0 # Adaptec AIC-6915 DuraLAN (``Starfire'') #device tl0 # Texas Instruments ThunderLAN #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vr0 # VIA Rhine, Rhine II #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wb0 # Winbond W89C840F device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 net irq 10 #device ex0 at isa? port? net irq? #device fe0 at isa? port 0x300 net irq ? #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 net irq 10 drq 0 #device cs0 at isa? port 0x300 net irq ? # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? port? net irq ? # PCCARD NIC drivers. # ze and zp take over the pcic and cannot coexist with generic pccard # support, nor the ed and ep drivers they replace. #device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support #pseudo-device sl 1 # Kernel SLIP #pseudo-device ppp 1 # Kernel PPP #pseudo-device tun 1 # Packet tunnel pseudo-device pty 16 # Pseudo-ttys (telnet etc) pseudo-device gzip # Exec gzipped a.out's # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter ##################################################################### # Spesialvalg for RAMSTIND # ##################################################################### options "NO_F00F_HACK" options DDB options DDB_UNATTENDED options PERFMON options KERNFS options QUOTA #pseudo-device speaker pseudo-device snp 4 #options CLK_USE_TSC_CALIBRATION #controller usb0 #controller uhci0 #controller ohci0 #device ugen0 #device uhid0 #device ukbd0 #device ulpt0 #device ums0 ##################################################################### # Slutt på spesialvalgene for RAMSTIND # ##################################################################### # Slutt på konfigurasjonsfilen RAMSTIND ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.4 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jan 19 18:40: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 5BEB315366 for ; Wed, 19 Jan 2000 18:40:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA06124; Wed, 19 Jan 2000 18:42:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001200242.SAA06124@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Dave Rynne Cc: freebsd-scsi@freebsd.org Subject: Re: Problems with Mylex eXtremeRAID 1100 (DAC 1164) In-reply-to: Your message of "Mon, 17 Jan 2000 17:21:06 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jan 2000 18:42:26 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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 When you say "takes a few mins to even boot", where is the time delay? Do you have the "BIOS" on the card enabled or disabled? I just cranked my DAC1164 up again, and -current as of today is working fine with it, so I need to gather some more information from you on this. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 20 18:22:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0141D15438 for ; Thu, 20 Jan 2000 18:22:56 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA81562 for ; Thu, 20 Jan 2000 19:22:45 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA07743 for ; Thu, 20 Jan 2000 19:22:41 -0700 (MST) Message-Id: <200001210222.TAA07743@harmony.village.org> To: freebsd-scsi@freebsd.org Subject: aha question Date: Thu, 20 Jan 2000 19:22:41 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org How important is hard wiring a aha device? I'm reworking the aha driver to support probing for the self identification and to better support plug and play. In order to do this, I have created an identify routine which scans all the devices in the traditional self probing order and adds device children as needed. The only problem with this that I can see is that it destroys the ability to hardwire aha instances to unit numbers in the config file. While no pci drivers support this, and the isa ep driver provide strong evidence that I don't need to support this, I thought I'd ask here. Also, if I need to support this, how would I go about doing that? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jan 20 18:45:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 677D61537B for ; Thu, 20 Jan 2000 18:45:52 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id VAA07501; Thu, 20 Jan 2000 21:45:43 -0500 (EST) Date: Thu, 20 Jan 2000 21:45:43 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: aha question In-Reply-To: <200001210222.TAA07743@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jan 2000, Warner Losh wrote: > How important is hard wiring a aha device? I'm reworking the aha > driver to support probing for the self identification and to better > support plug and play. In order to do this, I have created an > identify routine which scans all the devices in the traditional self > probing order and adds device children as needed. The only problem > with this that I can see is that it destroys the ability to hardwire > aha instances to unit numbers in the config file. While no pci > drivers support this, and the isa ep driver provide strong evidence > that I don't need to support this, I thought I'd ask here. Well, I'd argue that you don't need to support hardwired devices but thats only because I was too lazy to properly solve the possible contentions b/t devices found in the IDENTIFY and devices hardcoded and provided by the ISA hint mechanism. Basically, inside the loop of your IDENTIFY method you'll need something like this: while (find_cards) { found = look_for_card(address); if (found) { err = devclass_get_devices(devclass, &listp, &count); if (!err & count) for (i = 0; i < count; i++) { bus_get_resource(listp[i], SYS_RES_IOPORT, 0, &io_start, &io_count); if (io_start == address) { /* cleanup listp etc */ /* "He says they've already got one! */ continue; } } } } > Also, if I need to support this, how would I go about doing that? Like above. :) Good luck; if you implement this we should probably think about generalizing it so everyone can use it. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message