From owner-freebsd-hardware@FreeBSD.ORG Sat Mar 10 16:51:23 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD57E16A400 for ; Sat, 10 Mar 2007 16:51:23 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 7CDD613C441 for ; Sat, 10 Mar 2007 16:51:23 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.8/8.13.8) with ESMTP id l2AGpE5o070428; Sat, 10 Mar 2007 08:51:22 -0800 (PST) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.8/8.13.8/Submit) with ESMTP id l2AGpEbu070425; Sat, 10 Mar 2007 08:51:14 -0800 (PST) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Sat, 10 Mar 2007 08:51:12 -0800 (PST) From: mjacob@freebsd.org To: Mike Tancsa In-Reply-To: <200703101452.l2AEqdqq006832@lava.sentex.ca> Message-ID: <20070310085001.Q70411@ns1.feral.com> References: <200703091820.l29IKuwT001782@lava.sentex.ca> <20070309221943.I64099@ns1.feral.com> <200703101452.l2AEqdqq006832@lava.sentex.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hardware@freebsd.org Subject: Re: MPT SAS1064 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2007 16:51:23 -0000 Do you know what the actual attached disk(s) are? Can you get into the MPT BIOS and look at the RAID Properties tab if it exists? > At 01:21 AM 3/10/2007, mjacob@freebsd.org wrote: > > >> Haven't a clue- this doesn't appear to be the embedded mirroring adapter- >> which is good because you're lucky if it works at all for you. What's the >> actual underlying device? > > Hi, > Not sure how to find that out ? I dont see anything in dmesg or > pciconf other than what I included in the original email. > > ---Mike > > >>> | LSI Logic MPT Setup Utility v6.04.00.00 (2005.08.29) | >>> | Adapter List Global Properties | >>> | Adapter PCI PCI PCI PCI FW Revision Status Boot | >>> | Bus Dev Fnc Slot Order | >>> | SAS1064 03 01 00 02 1.06.00.00-IR Enabled 0 | >>> >>> [tyan-1u]% dmesg | grep mpt >>> mpt0: port 0xd800-0xd8ff mem >>> 0xdfefc000-0xdfefffff,0xdfee0000-0xdfeeffff irq 48 at device 1.0 on pci3 >>> mpt0: [GIANT-LOCKED] >>> mpt0: MPI Version=1.5.10.0 >>> mpt0: mpt_cam_event: 0xb >>> mpt0: Unhandled Event Notify Frame. Event 0xb (ACK not required). >>> da0 at mpt0 bus 0 target 8 lun 0 >>> [tyan-1u]% dmesg | grep da0 >>> da0 at mpt0 bus 0 target 8 lun 0 >>> da0: Fixed Direct Access SCSI-2 device >>> da0: 300.000MB/s transfers, Tagged Queueing Enabled >>> da0: 75340MB (154296320 512 byte sectors: 255H 63S/T 9604C) >>> [tyan-1u]% >>> >>> mpt0@pci3:1:0: class=0x010000 card=0x30201000 chip=0x00501000 rev=0x02 >>> hdr=0x00 >>> vendor = 'LSI Logic (Was: Symbios Logic, NCR)' >>> class = mass storage >>> subclass = SCSI >>> cap 01[50] = powerspec 2 supports D0 D1 D2 D3 current D0 >>> cap 05[98] = MSI supports 1 message, 64 bit >>> cap 07[68] = PCI-X 64-bit supports 133MHz, 2048 burst read, 16 split >>> transactions >>> cap 11[b0] = MSI-X supports 1 message in map 0x14 >>> >>> >>> -------------------------------------------------------------------- >>> Mike Tancsa, tel +1 519 651 3400 >>> Sentex Communications, mike@sentex.net >>> Providing Internet since 1994 www.sentex.net >>> Cambridge, Ontario Canada www.sentex.net/mike >>> > >