From owner-freebsd-scsi@FreeBSD.ORG Mon Jul 21 11:07:02 2008 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DB781065673 for ; Mon, 21 Jul 2008 11:07:02 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7C0748FC28 for ; Mon, 21 Jul 2008 11:07:02 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m6LB72ff032004 for ; Mon, 21 Jul 2008 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m6LB727r032000 for freebsd-scsi@FreeBSD.org; Mon, 21 Jul 2008 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Jul 2008 11:07:02 GMT Message-Id: <200807211107.m6LB727r032000@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2008 11:07:02 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/40895 scsi wierd kernel / device driver bug o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/60598 scsi wire down of scsi devices conflicts with config o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi 15 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce o kern/38828 scsi [dpt] [request] DPT PM2012B/90 doesn't work o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/119668 scsi [cam] [patch] certain errors are too verbose comparing o kern/120487 scsi [sg] scsi_sg incompatible with scanners o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/123666 scsi [aac] aac(4) will not work with Adaptec SAS RAID 3805 o kern/123674 scsi [ahc] ahc driver dumping 10 problems total. From owner-freebsd-scsi@FreeBSD.ORG Fri Jul 25 14:33:35 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FCB6106567B for ; Fri, 25 Jul 2008 14:33:35 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityweb.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id E0CD28FC2B for ; Fri, 25 Jul 2008 14:33:34 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from [127.0.0.1] ([70.88.211.149]) by portcityweb.com with MailEnable ESMTP; Fri, 25 Jul 2008 10:20:31 -0400 X-WatchGuard-Mail-Exception: Allow Message-ID: <4889E1DA.2070504@greatbaysoftware.com> Date: Fri, 25 Jul 2008 10:23:22 -0400 From: Charles Owens MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: multipart/mixed; boundary="------------090909080308060206080607" X-WatchGuard-AntiVirus: part scanned. clean action=allow X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: LSI LSLSAS1068 not detected by mpt(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2008 14:33:35 -0000 This is a multi-part message in MIME format. --------------090909080308060206080607 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow Good day, We're trying to get FreeBSD 7.0 to fly on an Intel SR2500ALLX server, but the RAID controller isn't being detected properly. As best I can tell from reading man pages it _should_ be being handled by mpt(4) -- but the system boots with no drives detected. Also, it is probably worth pointing out that the system has been working before this just fine with Linux. With pciconf I'm getting this: mfi0@pci0:4:14:0: class=0x010400 card=0x35018086 chip=0x04111000 rev=0x00 hdr=0x00 class = mass storage subclass = RAID I saw a commit message for mpt_pci.c from last Sept (rev 1.51 & mfc) that was a fix for a device ID conflict with mfi(4). Could this same sort of thing be happening here? What is the best way forward? Is a custom kernel with mfi(4) removed a possible workaround? Any assistance greatly appreciated! Thank you, Charles -- **Charles Owens** *Great Bay Software** **|** v: *603.766.6105 *|** m: *603.866.0860 *|** f: *603.430.0713 *|** e: *cowens@GreatBaySoftware.com**** --------------090909080308060206080607-- From owner-freebsd-scsi@FreeBSD.ORG Fri Jul 25 14:44:37 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3604D106566C for ; Fri, 25 Jul 2008 14:44:37 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 106A58FC2B for ; Fri, 25 Jul 2008 14:44:37 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 95E1E1A90E7; Fri, 25 Jul 2008 07:42:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id If5mpr+50QGk; Fri, 25 Jul 2008 07:42:19 -0700 (PDT) Received: from [10.47.1.10] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id 192AB1A90C2; Fri, 25 Jul 2008 07:42:19 -0700 (PDT) Message-ID: <4889E6D3.8000202@miralink.com> Date: Fri, 25 Jul 2008 07:44:35 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Charles Owens References: <4889E1DA.2070504@greatbaysoftware.com> In-Reply-To: <4889E1DA.2070504@greatbaysoftware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: LSI LSLSAS1068 not detected by mpt(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2008 14:44:37 -0000 Charles Owens wrote: > Good day, > > We're trying to get FreeBSD 7.0 to fly on an Intel SR2500ALLX server, > but the RAID controller isn't being detected properly. As best I can > tell from reading man pages it _should_ be being handled by mpt(4) -- > but the system boots with no drives detected. Also, it is probably > worth pointing out that the system has been working before this just > fine with Linux. > > With pciconf I'm getting this: > > mfi0@pci0:4:14:0: class=0x010400 card=0x35018086 chip=0x04111000 > rev=0x00 hdr=0x00 > class = mass storage > subclass = RAID > > > I saw a commit message for mpt_pci.c from last Sept (rev 1.51 & mfc) > that was a fix for a device ID conflict with mfi(4). Could this same > sort of thing be happening here? > What is the best way forward? Is a custom kernel with mfi(4) removed > a possible workaround? Any assistance greatly appreciated! > > Thank you, > > Charles > > ------------------------------------------------------------------------ > > Can you post the boot output(or at least as much as possible)? > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Cell 503-358-6832 Phone 503-621-5143 Fax 503-621-5199 MSN: sbruno@miralink.com Google: seanwbruno@gmail.com From owner-freebsd-scsi@FreeBSD.ORG Fri Jul 25 15:54:59 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAF521065675 for ; Fri, 25 Jul 2008 15:54:59 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityweb.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id A16638FC08 for ; Fri, 25 Jul 2008 15:54:59 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from [127.0.0.1] ([70.88.211.149]) by portcityweb.com with MailEnable ESMTP; Fri, 25 Jul 2008 11:54:55 -0400 X-WatchGuard-Mail-Exception: Allow Message-ID: <4889F7F9.9070203@greatbaysoftware.com> Date: Fri, 25 Jul 2008 11:57:45 -0400 From: Charles Owens MIME-Version: 1.0 To: Sean Bruno References: <4889E1DA.2070504@greatbaysoftware.com> <4889E6D3.8000202@miralink.com> In-Reply-To: <4889E6D3.8000202@miralink.com> Content-Type: multipart/mixed; boundary="------------050406030902010604020800" X-WatchGuard-AntiVirus: part scanned. clean action=allow X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-scsi@freebsd.org Subject: Re: LSI LSLSAS1068 not detected by mpt(4) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2008 15:54:59 -0000 This is a multi-part message in MIME format. --------------050406030902010604020800 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow Sean Bruno wrote: > Charles Owens wrote: >> Good day, >> >> We're trying to get FreeBSD 7.0 to fly on an Intel SR2500ALLX server, >> but the RAID controller isn't being detected properly. As best I can >> tell from reading man pages it _should_ be being handled by mpt(4) -- >> but the system boots with no drives detected. Also, it is probably >> worth pointing out that the system has been working before this just >> fine with Linux. >> >> With pciconf I'm getting this: >> >> mfi0@pci0:4:14:0: class=0x010400 card=0x35018086 chip=0x04111000 >> rev=0x00 hdr=0x00 >> class = mass storage >> subclass = RAID >> >> >> I saw a commit message for mpt_pci.c from last Sept (rev 1.51 & mfc) >> that was a fix for a device ID conflict with mfi(4). Could this same >> sort of thing be happening here? >> What is the best way forward? Is a custom kernel with mfi(4) removed >> a possible workaround? Any assistance greatly appreciated! >> >> Thank you, >> >> Charles >> >> ------------------------------------------------------------------------ >> > Can you post the boot output(or at least as much as possible)? > Ahem (blushing)... should have looked at the boot output before. It looks like it is being meaningfully probed by the _mfi_ driver. My very detailed Intel tech spec document very clearly says the 1068 controller... but from the boot output it would seem that this detail isn't accurate: mfi0: mem 0xb8b00000-0xb8b0ffff,0xb8900000-0xb891ffff irq 18 at device 14.0 on pci4 mfi0: Megaraid SAS driver Ver 2.00 mfi0: 946 (270205097s/0x0020/0) - Shutdown command received from host mfi0: 947 (4278190080s/0x0020/0) - PCI 0x041000 0x04411 0x048086 0x043501: Firmware initialization started (PCI ID 0411/1000/3501/8086) mfi0: 948 (4278190080s/0x0020/0) - Type 18: Firmware version 1.03.00-0211 mfi0: 949 (4278190091s/0x0008/0) - Battery temperature is normal mfi0: 950 (4278190092s/0x0008/1) - Battery requires reconditioning; please initiate a LEARN cycle mfi0: 951 (4278190092s/0x0008/0) - Battery Present mfi0: 952 (4278190137s/0x0004/0) - PD 12(e1/s255) event: Enclosure (SES) discovered on PD 0c(e1/s255) mfi0: 953 (4278190137s/0x0002/0) - PD 12(e1/s255) event: Inserted: PD 0c(e1/s255) mfi0: 954 (4278190137s/0x0002/0) - Type 29: Inserted: PD 0c(e1/s255) Info: enclPd=0c, scsiType=d, portMap=00, sasAddr=5000403d5b21a000,0000000000000000 mfi0: 955 (4278190137s/0x0002/0) - PD 08(e1/s0) event: Inserted: PD 08(e1/s0) mfi0: 956 (4278190137s/0x0002/0) - Type 29: Inserted: PD 08(e1/s0) Info: enclPd=0c, scsiType=0, portMap=01, sasAddr=5000c50008479ea5,0000000000000000 mfi0: 957 (4278190137s/0x0002/0) - PD 09(e1/s1) event: Inserted: PD 09(e1/s1) mfi0: 958 (4278190137s/0x0002/0) - Type 29: Inserted: PD 09(e1/s1) Info: enclPd=0c, scsiType=0, portMap=02, sasAddr=5000c5000847aadd,0000000000000000 mfi0: 959 (4278190137s/0x0002/0) - PD 10(e1/s2) event: Inserted: PD 0a(e1/s2) mfi0: 960 (4278190137s/0x0002/0) - Type 29: Inserted: PD 0a(e1/s2) Info: enclPd=0c, scsiType=0, portMap=04, sasAddr=5000c5000847c79d,0000000000000000 mfi0: 961 (4278190137s/0x0002/0) - PD 11(e1/s3) event: Inserted: PD 0b(e1/s3) mfi0: 962 (4278190137s/0x0002/0) - Type 29: Inserted: PD 0b(e1/s3) Info: enclPd=0c, scsiType=0, portMap=08, sasAddr=5000c50008478481,0000000000000000 mfi0: 963 (4278190138s/0x0008/1) - BBU disabled; changing WB virtual disks to WT mfi0: 964 (270290931s/0x0020/0) - Adapter ticks 270290931 elapsed 58s: Time established as 07/25/08 8:48:51; (58 seconds since power on) mfi0: [ITHREAD] ... mfid0: on mfi0 mfid0: 137328MB (281247744 sectors) RAID volume '' is optimal So... looks like there may be no issue... except the not-following-my-nose variety. Thanks, Charles **Charles Owens** *Great Bay Software** **|** v: *603.766.6105 *|** m: *603.866.0860 *|** f: *603.430.0713 *|** e: *cowens@GreatBaySoftware.com**** --------------050406030902010604020800-- From owner-freebsd-scsi@FreeBSD.ORG Fri Jul 25 20:12:30 2008 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80DE91065672 for ; Fri, 25 Jul 2008 20:12:30 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityweb.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 5F0418FC19 for ; Fri, 25 Jul 2008 20:12:30 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from [127.0.0.1] ([70.88.211.149]) by portcityweb.com with MailEnable ESMTP; Fri, 25 Jul 2008 16:12:26 -0400 X-WatchGuard-Mail-Exception: Allow Message-ID: <488A3455.2070505@greatbaysoftware.com> Date: Fri, 25 Jul 2008 16:15:17 -0400 From: Charles Owens MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: multipart/mixed; boundary="------------010000080503020201030900" X-WatchGuard-AntiVirus: part scanned. clean action=allow X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: mfi_linux.ko and PAE kernels X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2008 20:12:30 -0000 This is a multi-part message in MIME format. --------------010000080503020201030900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow Hello all, The man pages are pretty clear about not using kernel modules with PAE kernels.... I'm now trying to get mfi_linux to work with PAE but am not clear how to compile it statically in to the kernel (or even if I really should). I tried both "options MFI_LINUX" and "device mfi_linux" ... just guess work... and not surprisingly config(8) doesn't like either. So what's the secret? Am I on the right track? Or is loading it as module okay? (but if so, why not other modules?) Thanks much, Charles -- **Charles Owens** *Great Bay Software** **|** v: *603.766.6105 *|** m: *603.866.0860 *|** f: *603.430.0713 *|** e: *cowens@GreatBaySoftware.com**** --------------010000080503020201030900--