From owner-freebsd-scsi@FreeBSD.ORG Sun Jan 23 05:54:17 2011 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 12F5B106566B for ; Sun, 23 Jan 2011 05:54:17 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id AD3C18FC0C for ; Sun, 23 Jan 2011 05:54:16 +0000 (UTC) Received: from [192.168.1.100] (m206-63.dsl.tsoft.com [198.144.206.63]) by ns1.feral.com (8.14.4/8.14.3) with ESMTP id p0N5sFXY035510; Sat, 22 Jan 2011 21:54:15 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4D3BC293.4010808@feral.com> Date: Sat, 22 Jan 2011 21:54:27 -0800 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: pz-freebsd-scsi@ziemba.us References: In-Reply-To: Content-Type: multipart/mixed; boundary="------------070101080802070005040808" X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.67.166.1]); Sat, 22 Jan 2011 21:54:15 -0800 (PST) Cc: freebsd-scsi@freebsd.org Subject: Re: rescan causes offlined tape to reload 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: Sun, 23 Jan 2011 05:54:17 -0000 This is a multi-part message in MIME format. --------------070101080802070005040808 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 1/20/2011 2:33 PM, G. Paul Ziemba wrote: The basic gist of the error is that during the probe sequence a command is likely coming back with ASC 0x04 ASCQ 0x02 (Logical unit not ready, initializing command required). Unfortunately, this causes camperiphscsisenseerror to issue scsi_start_stop command. Why this did not occur before I am a little baffled about because the same code was in place in the time frame you had it 'working'. See if the attached patch helps --------------070101080802070005040808 Content-Type: text/plain; name="no_auto_start.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="no_auto_start.patch" Index: sys/cam/cam_periph.c =================================================================== --- sys/cam/cam_periph.c (revision 217716) +++ sys/cam/cam_periph.c (working copy) @@ -1525,36 +1525,43 @@ *action_string = "Unretryable error"; break; case SS_START: - { - int le; + if (SID_TYPE(&cgd.inq_data) != T_SEQUENTIAL) { + int le; - /* - * Send a start unit command to the device, and - * then retry the command. - */ - *action_string = "Attempting to start unit"; - periph->flags |= CAM_PERIPH_RECOVERY_INPROG; + /* + * Send a start unit command to the device, and + * then retry the command. + */ + *action_string = "Attempting to start unit"; + periph->flags |= CAM_PERIPH_RECOVERY_INPROG; - /* - * Check for removable media and set - * load/eject flag appropriately. - */ - if (SID_IS_REMOVABLE(&cgd.inq_data)) - le = TRUE; - else - le = FALSE; + /* + * Check for removable media and set + * load/eject flag appropriately. + */ + if (SID_IS_REMOVABLE(&cgd.inq_data)) + le = TRUE; + else + le = FALSE; - scsi_start_stop(&ccb->csio, - /*retries*/1, - camperiphdone, - MSG_SIMPLE_Q_TAG, - /*start*/TRUE, - /*load/eject*/le, - /*immediate*/FALSE, - SSD_FULL_SIZE, - /*timeout*/50000); + scsi_start_stop(&ccb->csio, + /*retries*/1, + camperiphdone, + MSG_SIMPLE_Q_TAG, + /*start*/TRUE, + /*load/eject*/le, + /*immediate*/FALSE, + SSD_FULL_SIZE, + /*timeout*/50000); + } else { + xpt_free_ccb(orig_ccb); + ccb->ccb_h.status |= CAM_DEV_QFRZN; + *action_string = "Will not autostart a " + "sequential access device"; + err_action = SS_FAIL; + error = EIO; + } break; - } case SS_TUR: { /* --------------070101080802070005040808-- From owner-freebsd-scsi@FreeBSD.ORG Sun Jan 23 09:46:38 2011 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 85765106566B for ; Sun, 23 Jan 2011 09:46:38 +0000 (UTC) (envelope-from pz-freebsd-scsi@ziemba.us) Received: from ziemba.us (osmtp.ziemba.us [208.106.105.149]) by mx1.freebsd.org (Postfix) with ESMTP id 5AC6D8FC14 for ; Sun, 23 Jan 2011 09:46:38 +0000 (UTC) Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1]) by hairball.ziemba.us (8.14.4/8.14.4) with ESMTP id p0N9kb0i009844 for ; Sun, 23 Jan 2011 01:46:37 -0800 (PST) (envelope-from pz-freebsd-scsi@ziemba.us) Received: (from mailnull@localhost) by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p0N9kbdv009843 for freebsd-scsi@freebsd.org; Sun, 23 Jan 2011 01:46:37 -0800 (PST) (envelope-from pz-freebsd-scsi@ziemba.us) X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to pz-freebsd-scsi@ziemba.us using -f Received: (from news@localhost) by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p0N9kb1u009807 for treehouse-mail-freebsd-scsi@hairball.treehouse.napa.ca.us; Sun, 23 Jan 2011 01:46:37 -0800 (PST) (envelope-from news) From: "G. Paul Ziemba" To: freebsd-scsi@freebsd.org Date: Sun, 23 Jan 2011 09:46:37 +0000 (UTC) Message-id: References: <4D3BC293.4010808@feral.com> Errors-to: "G. Paul Ziemba" Subject: Re: rescan causes offlined tape to reload X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paul+usenet@w6yx.stanford.edu List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2011 09:46:38 -0000 mj@feral.com (Matthew Jacob) writes: >The basic gist of the error is that during the probe sequence a command >is likely coming back with ASC 0x04 ASCQ 0x02 (Logical unit not ready, >initializing command required). >Unfortunately, this causes camperiphscsisenseerror to issue >scsi_start_stop command. >See if the attached patch helps Matthew, thanks for your efforts on this issue. It seems to avoid reloading the tape when there is a rescan (yay!) I have not had a chance to fully exercise it (it might take until Monday before I can run it through my usual sequence of operations) however so I can't say what else will happen. But now there is a TUR about every two seconds. (Maybe because "error = EIO;" on line 1562 bubbles up and causes a retry?) >Why this did not occur before I am a little >baffled about because the same code was in place in the time frame you >had it 'working'. I'll see if I can rebuild an old kernel from Nov 2009 -stable. Maybe it will even work with a Jan 2011 world/ports. -- G. Paul Ziemba FreeBSD unix: 1:46AM up 1:04, 6 users, load averages: 0.09, 0.21, 0.16 From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 24 11:07:09 2011 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 DFCB5106570B for ; Mon, 24 Jan 2011 11:07:08 +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 CE23A8FC26 for ; Mon, 24 Jan 2011 11:07:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p0OB78ql077914 for ; Mon, 24 Jan 2011 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p0OB78CJ077912 for freebsd-scsi@FreeBSD.org; Mon, 24 Jan 2011 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Jan 2011 11:07:08 GMT Message-Id: <201101241107.p0OB78CJ077912@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, 24 Jan 2011 11:07:09 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/153361 scsi [ciss] Smart Array 5300 boot/detect drive problem o kern/152250 scsi [ciss] [patch] Kernel panic when hw.ciss.expose_hidden o kern/151564 scsi [ciss] ciss(4) should increase CISS_MAX_LOGICAL to 10 o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c o kern/148083 scsi [aac] Strange device reporting o kern/147704 scsi [mpt] sys/dev/mpt: new chip revision, partially unsupp o kern/146287 scsi [ciss] ciss(4) cannot see more than one SmartArray con o kern/145768 scsi [mpt] can't perform I/O on SAS based SAN disk in freeb o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/144301 scsi [ciss] [hang] HP proliant server locks when using ciss o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/141934 scsi [cam] [patch] add support for SEAGATE DAT Scopion 130 o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/127717 scsi [ata] [patch] [request] - support write cache toggling o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping o kern/123520 scsi [ahd] unable to boot from net while using ahd o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o bin/57088 scsi [cam] [patch] for a possible fd leak in libcam.c o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/40895 scsi wierd kernel / device driver bug o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 45 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 24 16:01:11 2011 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 9BDFF1065672; Mon, 24 Jan 2011 16:01:11 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 627548FC15; Mon, 24 Jan 2011 16:01:11 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id p0OG1A49080781; Mon, 24 Jan 2011 09:01:10 -0700 (MST) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id p0OG1A9J080780; Mon, 24 Jan 2011 09:01:10 -0700 (MST) (envelope-from ken) Date: Mon, 24 Jan 2011 09:01:10 -0700 From: "Kenneth D. Merry" To: Joachim Tingvold Message-ID: <20110124160110.GA77711@nargothrond.kdm.org> References: <4D2DAA45.30602@FreeBSD.org> <41C64262-4300-4187-B5FD-04A5EFB7F87C@tingvold.com> <20110113203750.GA39494@nargothrond.kdm.org> <20110114001758.GA12793@nargothrond.kdm.org> <07392102-4584-4690-9188-5202728CC7CA@tingvold.com> <20110120155746.GA22515@nargothrond.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Cc: freebsd-scsi@freebsd.org, Alexander Motin Subject: Re: mps0-troubles 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, 24 Jan 2011 16:01:11 -0000 On Fri, Jan 21, 2011 at 20:15:15 +0100, Joachim Tingvold wrote: > On Thu, Jan 20, 2011, at 16:57:46PM GMT+01:00, Kenneth D. Merry wrote: > >So did the system freeze or crash this time? > > It happened while I was not actively using the machine. When I found > out about it, everything seemed to be fine. Okay, so that means it didn't panic and didn't lock up permanently, so things are probably okay. > >Do you have a serial console on the machine? > >If it hangs or crashes, perhaps we can get a stack trace. > > You mean normal RS-232? Yes. > >It does look like the out of chain problem was fixed by increasing the > >number, so that's good at least. > > Yes. For now, at least. (-: Yes. It looks like you're just getting some timeouts, followed by aborts and retries. It's not optimal, but at least the system is recovering and continuing on. FWIW, there is some much more sophisticated error recovery code coming for the driver, written by the guys at Isilon. That'll come in when LSI gets done with their version of the driver. The error recovery that is in there now is basic, but it works in most of the common cases. There is a case related to device removal that Justin fixed that I'm planning to commit in the near future. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 24 16:57:16 2011 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 B5B48106566C for ; Mon, 24 Jan 2011 16:57:16 +0000 (UTC) (envelope-from pz-freebsd-scsi@ziemba.us) Received: from ziemba.us (osmtp.ziemba.us [208.106.105.149]) by mx1.freebsd.org (Postfix) with ESMTP id 8972B8FC14 for ; Mon, 24 Jan 2011 16:57:16 +0000 (UTC) Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1]) by hairball.ziemba.us (8.14.4/8.14.4) with ESMTP id p0OGvFNA084963 for ; Mon, 24 Jan 2011 08:57:15 -0800 (PST) (envelope-from pz-freebsd-scsi@ziemba.us) Received: (from mailnull@localhost) by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p0OGvFmI084962 for freebsd-scsi@freebsd.org; Mon, 24 Jan 2011 08:57:15 -0800 (PST) (envelope-from pz-freebsd-scsi@ziemba.us) X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to pz-freebsd-scsi@ziemba.us using -f Received: (from news@localhost) by hairball.ziemba.us (8.14.4/8.14.4/Submit) id p0OGvF2h084928 for treehouse-mail-freebsd-scsi@hairball.treehouse.napa.ca.us; Mon, 24 Jan 2011 08:57:15 -0800 (PST) (envelope-from news) From: "G. Paul Ziemba" To: freebsd-scsi@freebsd.org Date: Mon, 24 Jan 2011 16:57:15 +0000 (UTC) Message-id: References: <4D3BC293.4010808@feral.com> Errors-to: "G. Paul Ziemba" Subject: Re: rescan causes offlined tape to reload X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: paul+usenet@w6yx.stanford.edu List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2011 16:57:16 -0000 pz-freebsd-scsi@ziemba.us ("G. Paul Ziemba") writes: >mj@feral.com (Matthew Jacob) writes: >>The basic gist of the error is that during the probe sequence a command >>is likely coming back with ASC 0x04 ASCQ 0x02 (Logical unit not ready, >>initializing command required). >>Unfortunately, this causes camperiphscsisenseerror to issue >>scsi_start_stop command. >>See if the attached patch helps >Matthew, thanks for your efforts on this issue. I exercised this code a bit more yesterday, and it seems to do the right thing (i.e., "camcontrol rescan" no longer causes the tape to load). I'm delighted! However it does seem to continually (every two seconds) send a TUR to the tape drive. That doesn't cause an operational problem, but might not be what you intended. Popping up a level, about optical (cd/dvd) drives: should those behave differently? It's not an operational issue for me, but should optical drives load on a rescan either? Meanwhile, I'll see if I can get a stable kernel from Dec 2009 or so built so I can look at the old behavior. I think I can run it in single user mode to avoid issues with the more recent ports+world. thanks, ~!paul -- G. Paul Ziemba FreeBSD unix: 8:56AM up 1 day, 8:14, 6 users, load averages: 0.03, 0.05, 0.02 From owner-freebsd-scsi@FreeBSD.ORG Mon Jan 24 19:53:07 2011 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 195D3106564A for ; Mon, 24 Jan 2011 19:53:07 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id D9AC98FC12 for ; Mon, 24 Jan 2011 19:53:06 +0000 (UTC) Received: from [192.168.221.2] (remotevpn [192.168.221.2]) by ns1.feral.com (8.14.4/8.14.3) with ESMTP id p0OJr3PE053398 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 24 Jan 2011 11:53:05 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4D3DD89D.3030504@feral.com> Date: Mon, 24 Jan 2011 11:53:01 -0800 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4D3BC293.4010808@feral.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.6 (ns1.feral.com [192.168.221.1]); Mon, 24 Jan 2011 11:53:06 -0800 (PST) Subject: Re: rescan causes offlined tape to reload 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, 24 Jan 2011 19:53:07 -0000 > However it does seem to continually (every two seconds) send a TUR > to the tape drive. That doesn't cause an operational problem, but > might not be what you intended. This is fixable. > Popping up a level, about optical (cd/dvd) drives: should those > behave differently? It's not an operational issue for me, but > should optical drives load on a rescan either? > > Policy is not clear here. From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 26 09:08:03 2011 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 3CBD1106566C for ; Wed, 26 Jan 2011 09:08:03 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop2b.sarenet.es (proxypop2b.sarenet.es [194.30.0.107]) by mx1.freebsd.org (Postfix) with ESMTP id CA8358FC0C for ; Wed, 26 Jan 2011 09:08:02 +0000 (UTC) Received: from [172.16.1.55] (ssglan.sare.net [192.148.167.100]) by proxypop2b.sarenet.es (Postfix) with ESMTP id ECE8E732D3; Wed, 26 Jan 2011 10:08:00 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20110120170046.GA40879@nargothrond.kdm.org> Date: Wed, 26 Jan 2011 10:08:01 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20110120170046.GA40879@nargothrond.kdm.org> To: Kenneth D. Merry X-Mailer: Apple Mail (2.1082) Cc: freebsd-scsi@freebsd.org Subject: Re: mps questions 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: Wed, 26 Jan 2011 09:08:03 -0000 On Jan 20, 2011, at 6:00 PM, Kenneth D. Merry wrote: >> And this happens no matter how I connect the internal SAS connectors. = There are two connectors from the disk backplanes to the card, SAS0 and = SAS1 (I assume they are two buses) and even if I reverse them I still = see eight disks.=20 >>=20 >=20 > I assume you mean you still see six disks... Yes, sorry :) Neuron short circuit. > If you see all the disks in the LSI BIOS, it most likely means there = is a > driver bug that is keeping FreeBSD from seeing all the disks. >=20 > Try booting with -v (boot -v at the boot loader prompt) and send the = full > dmesg output. That will cause the driver to print some additional > information when it probes. The dmesg is rather long, but maybe the list of mps related messages wil = be enough? (output follows at the end of the message) > After that, try booting with hw.mps.N.debug_level=3D1 set in = loader.conf, > where N is either 0 or 1, depending on which mps instance is having = the > problem. >=20 > You can turn it off via sysctl after you boot. Next thing to try :) boot -v yields the following messages. Curious thing, I don't see the = backplane as a device. Shouldn't it show up? I guess it would be that = "edge expander" Jan 26 09:30:26 kernel: mps0: port 0xfc00-0xfcff mem = 0xdf2b0000-0xdf2bffff,0xdf2c0000-0xdf2fffff irq 32 at device 0.0 on pci2 Jan 26 09:30:26 kernel: mps0: Reserved 0x10000 bytes for rid 0x14 type = 3 at 0xdf2b0000 Jan 26 09:30:26 kernel: mps0: Firmware: 02.15.63.00 Jan 26 09:30:26 kernel: mps0: IOCCapabilities: = 185c Jan 26 09:30:26 kernel: mps0: attempting to allocate 1 MSI-X vectors = (15 supported) Jan 26 09:30:26 kernel: mps0: using IRQ 258 for MSI-X Jan 26 09:30:26 kernel: mps0: [MPSAFE] Jan 26 09:30:26 kernel: mps0: [ITHREAD] Jan 26 09:30:26 kernel: mps0: Found device = <1902,Edge Expander> <6.0Gbps> <0x000a> <2/0> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000b> <2/0> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000c> <2/4> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000d> <2/5> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000e> <2/1> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x000f> <2/2> Jan 26 09:30:26 kernel: mps0: Found device ,End = Device> <6.0Gbps> <0x0010> <2/3> Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Down reving Protocol = Version from 4 to 2? Jan 26 09:30:26 kernel: (probe0:mps0:0:0:0): Error 22, Unretryable = error Jan 26 09:30:26 kernel: pass0 at mps0 bus 0 scbus0 target 1 lun 0 Jan 26 09:30:26 kernel: pass1 at mps0 bus 0 scbus0 target 2 lun 0 Jan 26 09:30:26 kernel: pass2 at mps0 bus 0 scbus0 target 3 lun 0 Jan 26 09:30:26 kernel: pass3 at mps0 bus 0 scbus0 target 4 lun 0 Jan 26 09:30:26 kernel: pass4 at mps0 bus 0 scbus0 target 5 lun 0 Jan 26 09:30:26 kernel: pass5 at mps0 bus 0 scbus0 target 6 lun 0 Jan 26 09:30:26 kernel: da0 at mps0 bus 0 scbus0 target 1 lun 0 Jan 26 09:30:26 kernel: da1 at mps0 bus 0 scbus0 target 2 lun 0 Jan 26 09:30:26 kernel: da2 at mps0 bus 0 scbus0 target 3 lun 0 Jan 26 09:30:26 kernel: da3 at mps0 bus 0 scbus0 target 4 lun 0 Jan 26 09:30:26 kernel: da4 at mps0 bus 0 scbus0 target 5 lun 0 Jan 26 09:30:26 kernel: da5 at mps0 bus 0 scbus0 target 6 lun 0 #=20 From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 26 10:17:01 2011 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 406EA1065670; Wed, 26 Jan 2011 10:17:01 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop1b.sarenet.es (proxypop1b.sarenet.es [194.30.0.104]) by mx1.freebsd.org (Postfix) with ESMTP id 5D69B8FC08; Wed, 26 Jan 2011 10:16:58 +0000 (UTC) Received: from [172.16.1.55] (ssglan.sare.net [192.148.167.100]) by proxypop1b.sarenet.es (Postfix) with ESMTP id 910095DD9; Wed, 26 Jan 2011 11:16:57 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20110120170046.GA40879@nargothrond.kdm.org> Date: Wed, 26 Jan 2011 11:16:57 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <13EDCBDE-6C2C-4CE5-9B0E-7FCF6FB02FA1@sarenet.es> References: <20110120170046.GA40879@nargothrond.kdm.org> To: Kenneth D. Merry X-Mailer: Apple Mail (2.1082) Cc: freebsd-scsi@freebsd.org Subject: Re: mps questions 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: Wed, 26 Jan 2011 10:17:01 -0000 On Jan 20, 2011, at 6:00 PM, Kenneth D. Merry wrote: > If you see all the disks in the LSI BIOS, it most likely means there = is a > driver bug that is keeping FreeBSD from seeing all the disks. >=20 > Try booting with -v (boot -v at the boot loader prompt) and send the = full > dmesg output. That will cause the driver to print some additional > information when it probes. >=20 > After that, try booting with hw.mps.N.debug_level=3D1 set in = loader.conf, > where N is either 0 or 1, depending on which mps instance is having = the > problem. >=20 > You can turn it off via sysctl after you boot. Sorry, more complete output follows. boot -v and debug enabled for the = driver. I've omitted plenty of "mps0: writing postindex NNN" messages # cat /var/run/dmesg.boot | fgrep -v "mps0: writing postindex" lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Da, irq=3D6 map[20]: type I/O Port, range 32, base 0xec80, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 21 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xec80 found-> vendor=3D0x8086, dev=3D0x3a35, revid=3D0x00 domain=3D0, bus=3D0, slot=3D29, func=3D1 class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x0290, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Db, irq=3D5 map[20]: type I/O Port, range 32, base 0xeca0, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 20 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xeca0 found-> vendor=3D0x8086, dev=3D0x3a36, revid=3D0x00 domain=3D0, bus=3D0, slot=3D29, func=3D2 class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x0290, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Dc, irq=3D6 map[20]: type I/O Port, range 32, base 0xecc0, size 5, enabled pcib0: matched entry for 0.29.INTC pcib0: slot 29 INTC hardwired to IRQ 21 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xecc0 found-> vendor=3D0x8086, dev=3D0x3a39, revid=3D0x00 domain=3D0, bus=3D0, slot=3D29, func=3D3 class=3D0c-03-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x0290, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Dd, irq=3D5 map[20]: type I/O Port, range 32, base 0xece0, size 5, enabled pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 20 unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xece0 found-> vendor=3D0x8086, dev=3D0x3a3a, revid=3D0x00 domain=3D0, bus=3D0, slot=3D29, func=3D7 class=3D0c-03-20, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0146, statreg=3D0x0290, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Da, irq=3D6 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xdf0ff000, size 10, = enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 21 unknown: Reserved 0x400 bytes for rid 0x10 type 3 at 0xdf0ff000 found-> vendor=3D0x8086, dev=3D0x244e, revid=3D0x90 domain=3D0, bus=3D0, slot=3D30, func=3D0 class=3D06-04-01, hdrtype=3D0x01, mfdev=3D0 cmdreg=3D0x0147, statreg=3D0x0010, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x0b (2750 ns), maxlat=3D0x00 = (0 ns) found-> vendor=3D0x8086, dev=3D0x3a16, revid=3D0x00 domain=3D0, bus=3D0, slot=3D31, func=3D0 class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0147, statreg=3D0x0210, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) pcib1: at device 1.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xda000000-0xddffffff pcib1: no prefetched decode pci1: on pcib1 pci1: domain=3D0, physical bus=3D1 found-> vendor=3D0x14e4, dev=3D0x163b, revid=3D0x20 domain=3D0, bus=3D1, slot=3D0, func=3D0 class=3D02-00-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0006, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Da, irq=3D15 powerspec 3 supports D0 D3 current D0 MSI supports 16 messages, 64 bit MSI-X supports 9 messages in map 0x10 map[10]: type Memory, range 64, base 0xda000000, size 25, = enabled pcib1: requested memory range 0xda000000-0xdbffffff: good pcib1: matched entry for 1.0.INTA pcib1: slot 0 INTA hardwired to IRQ 36 found-> vendor=3D0x14e4, dev=3D0x163b, revid=3D0x20 domain=3D0, bus=3D1, slot=3D0, func=3D1 class=3D02-00-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0006, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Db, irq=3D14 powerspec 3 supports D0 D3 current D0 MSI supports 16 messages, 64 bit MSI-X supports 9 messages in map 0x10 map[10]: type Memory, range 64, base 0xdc000000, size 25, = enabled pcib1: requested memory range 0xdc000000-0xddffffff: good pcib1: matched entry for 1.0.INTB pcib1: slot 0 INTB hardwired to IRQ 48 bce0: mem = 0xda000000-0xdbffffff irq 36 at device 0.0 on pci1 bce0: Reserved 0x2000000 bytes for rid 0x10 type 3 at 0xda000000 bce0: attempting to allocate 1 MSI vectors (16 supported) msi: routing MSI IRQ 256 to local APIC 32 vector 64 bce0: using IRQ 256 for MSI miibus0: on bce0 brgphy0: PHY 1 on miibus0 brgphy0: OUI 0x0050ef, model 0x003c, rev. 8 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bce0: bpf attached bce0: Ethernet address: 84:2b:2b:73:12:1f bce0: [MPSAFE] bce0: [ITHREAD] bce0: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (5.2.3); = Flags (MSI|MFW); MFW (NCSI 2.0.10) bce1: mem = 0xdc000000-0xddffffff irq 48 at device 0.1 on pci1 bce1: Reserved 0x2000000 bytes for rid 0x10 type 3 at 0xdc000000 bce1: attempting to allocate 1 MSI vectors (16 supported) msi: routing MSI IRQ 257 to local APIC 32 vector 80 bce1: using IRQ 257 for MSI miibus1: on bce1 brgphy1: PHY 1 on miibus1 brgphy1: OUI 0x0050ef, model 0x003c, rev. 8 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bce1: bpf attached bce1: Ethernet address: 84:2b:2b:73:12:20 bce1: [MPSAFE] bce1: [ITHREAD] bce1: ASIC (0x57092008); Rev (C0); Bus (PCIe x4, 2.5Gbps); B/C (5.2.3); = Flags (MSI|MFW); MFW (NCSI 2.0.10) pcib2: at device 3.0 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xf000-0xffff pcib2: memory decode 0xdf100000-0xdf2fffff pcib2: no prefetched decode pci2: on pcib2 pci2: domain=3D0, physical bus=3D2 found-> vendor=3D0x1000, dev=3D0x0072, revid=3D0x02 domain=3D0, bus=3D2, slot=3D0, func=3D0 class=3D01-07-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0007, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 = ns) intpin=3Da, irq=3D15 powerspec 3 supports D0 D1 D2 D3 current D0 MSI supports 1 message, 64 bit MSI-X supports 15 messages in map 0x14 map[10]: type I/O Port, range 32, base 0xfc00, size 8, enabled pcib2: requested I/O range 0xfc00-0xfcff: in range map[14]: type Memory, range 64, base 0xdf2b0000, size 16, = enabled pcib2: requested memory range 0xdf2b0000-0xdf2bffff: good map[1c]: type Memory, range 64, base 0xdf2c0000, size 18, = enabled pcib2: requested memory range 0xdf2c0000-0xdf2fffff: good pcib2: matched entry for 2.0.INTA pcib2: slot 0 INTA hardwired to IRQ 32 mps0: port 0xfc00-0xfcff mem = 0xdf2b0000-0xdf2bffff,0xdf2c0000-0xdf2fffff irq 32 at device 0.0 on pci2 mps0: Reserved 0x10000 bytes for rid 0x14 type 3 at 0xdf2b0000 mps0: Doorbell=3D 0x22000000 mps0: Doorbell=3D 0x12000000 mps0: IOCFacts : MsgVersion: 0x200 HeaderVersion: 0xb00 IOCNumber: 0 IOCExceptions: 0x0 MaxChainDepth: 96 WhoInit: ROM BIOS NumberOfPorts: 1 RequestCredit: 3439 ProductID: 0x2713 IOCCapabilities: = 185c FWVersion=3D 2-15-63-0 IOCRequestFrameSize: 32 MaxInitiators: 1 MaxTargets: 40 MaxSasExpanders: 20 MaxEnclosures: 10 ProtocolFlags: 3 HighPriorityCredit: 63 MaxReplyDescriptorPostQueueDepth: 65520 ReplyFrameSize: 32 MaxVolumes: 2 MaxDevHandle: 79 MaxPersistentEntries: 128 mps0: Firmware: 02.15.63.00 mps0: IOCCapabilities: = 185c mps0: Doorbell=3D 0x10000000 mps0: Doorbell=3D 0x10000000 mps0: IOCInit status=3D 0x0 mps0: PortFacts : PortNumber: 0 PortType: 0x30 MaxPostedCmdBuffers: 0 mps0: attempting to allocate 1 MSI-X vectors (15 supported) msi: routing MSI-X IRQ 258 to local APIC 32 vector 49 mps0: using IRQ 258 for MSI-X mps0: [MPSAFE] mps0: [ITHREAD] pcib3: at device 7.0 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xf000-0xfff pcib3: no prefetched decode pci3: on pcib3 pci3: domain=3D0, physical bus=3D3 pcib4: at device 9.0 on pci0 pcib4: domain 0 pcib4: secondary bus 4 pcib4: subordinate bus 4 pcib4: I/O decode 0xf000-0xfff pcib4: no prefetched decode pci4: on pcib4 pci4: domain=3D0, physical bus=3D4 pcib5: at device 10.0 on pci0 pcib5: domain 0 pcib5: secondary bus 5 pcib5: subordinate bus 5 pcib5: I/O decode 0xf000-0xfff pcib5: no prefetched decode pci5: on pcib5 pci5: domain=3D0, physical bus=3D5 pci0: at device 20.0 (no driver = attached) pci0: at device 20.1 (no driver = attached) pci0: at device 20.2 (no driver = attached) uhci0: port 0xec40-0xec5f = irq 17 at device 26.0 on pci0 ioapic0: routing intpin 17 (PCI IRQ 17) to lapic 32 vector 50 uhci0: [MPSAFE] uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0xec60-0xec7f = irq 18 at device 26.1 on pci0 ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 32 vector 51 uhci1: [MPSAFE] uhci1: [ITHREAD] usbus1: on uhci1 ehci0: mem = 0xdf0fe000-0xdf0fe3ff irq 19 at device 26.7 on pci0 ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 32 vector 52 ehci0: [MPSAFE] ehci0: [ITHREAD] usbus2: EHCI version 1.0 usbus2: on ehci0 uhci2: port 0xec80-0xec9f = irq 21 at device 29.0 on pci0 ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 32 vector 53 uhci2: [MPSAFE] uhci2: [ITHREAD] usbus3: on uhci2 uhci3: port 0xeca0-0xecbf = irq 20 at device 29.1 on pci0 ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 32 vector 54 uhci3: [MPSAFE] uhci3: [ITHREAD] usbus4: on uhci3 uhci4: port 0xecc0-0xecdf = irq 21 at device 29.2 on pci0 uhci4: [MPSAFE] uhci4: [ITHREAD] usbus5: on uhci4 uhci5: port 0xece0-0xecff = irq 20 at device 29.3 on pci0 uhci5: [MPSAFE] uhci5: [ITHREAD] usbus6: on uhci5 ehci1: mem = 0xdf0ff000-0xdf0ff3ff irq 21 at device 29.7 on pci0 ehci1: [MPSAFE] ehci1: [ITHREAD] usbus7: EHCI version 1.0 usbus7: on ehci1 pcib6: at device 30.0 on pci0 pcib6: domain 0 pcib6: secondary bus 6 pcib6: subordinate bus 6 pcib6: I/O decode 0xf000-0xfff pcib6: memory decode 0xde000000-0xdeffffff pcib6: prefetched decode 0xd9800000-0xd9ffffff pcib6: Subtractively decoded bridge. pci6: on pcib6 pci6: domain=3D0, physical bus=3D6 found-> vendor=3D0x102b, dev=3D0x0532, revid=3D0x0a domain=3D0, bus=3D6, slot=3D3, func=3D0 class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0007, statreg=3D0x0290, cachelnsz=3D16 (dwords) lattimer=3D0x20 (960 ns), mingnt=3D0x10 (4000 ns), maxlat=3D0x20 = (8000 ns) intpin=3Da, irq=3D10 powerspec 1 supports D0 D3 current D0 map[10]: type Prefetchable Memory, range 32, base 0xd9800000, = size 23, enabled pcib6: requested memory range 0xd9800000-0xd9ffffff: good map[14]: type Memory, range 32, base 0xde7fc000, size 14, = enabled pcib6: requested memory range 0xde7fc000-0xde7fffff: good map[18]: type Memory, range 32, base 0xde800000, size 23, = enabled pcib6: requested memory range 0xde800000-0xdeffffff: good pcib6: matched entry for 6.3.INTA pcib6: slot 3 INTA hardwired to IRQ 19 vgapci0: mem = 0xd9800000-0xd9ffffff,0xde7fc000-0xde7fffff,0xde800000-0xdeffffff irq 19 = at device 3.0 on pci6 isab0: at device 31.0 on pci0 isa0: on isab0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on = acpi0 acpi_hpet0: vend: 0x8086 rev: 0x1 num: 4 hz: 14318180 opts: legacy_route = 64-bit Timecounter "HPET" frequency 14318180 Hz quality 900 atrtc0: port 0x70-0x7f irq 8 on acpi0 atrtc0: registered as a time-of-day clock (resolution 1000000us) uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 32 vector 55 uart0: [FILTER] uart0: fast interrupt uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 ioapic0: routing intpin 3 (ISA IRQ 3) to lapic 32 vector 56 uart1: [FILTER] uart1: fast interrupt qpi0: on motherboard acpi0: wakeup code va 0xffffff8241e8c000 pa 0x4000 ex_isa_identify() ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed isa_probe_children: disabling PnP devices atrtc: atrtc0 already exists; skipping it sc: sc0 already exists; skipping it uart: uart0 already exists; skipping it uart: uart1 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: at iomem = 0xc0000-0xc7fff,0xc8000-0xc8fff,0xd2000-0xd2fff,0xec000-0xeffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0xffffffff (1) atkbd: failed to reset the keyboard. kbd0: atkbd0, AT 84 (1), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 32 vector 57 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:0045 psm0: failed to reset the aux device. fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 isa_probe_children: probing PnP devices est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 11 device_attach: est0 attach returned 6 p4tcc0: on cpu0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 10 device_attach: est1 attach returned 6 p4tcc1: on cpu1 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 11 device_attach: est2 attach returned 6 p4tcc2: on cpu2 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 11 device_attach: est3 attach returned 6 p4tcc3: on cpu3 est4: on cpu4 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 11 device_attach: est4 attach returned 6 p4tcc4: on cpu4 est5: on cpu5 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 11 device_attach: est5 attach returned 6 p4tcc5: on cpu5 est6: on cpu6 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 10 device_attach: est6 attach returned 6 p4tcc6: on cpu6 est7: on cpu7 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 10 device_attach: est7 attach returned 6 p4tcc7: on cpu7 Device configuration finished. procfs registered ZFS filesystem version 5 ZFS storage pool version 28 lapic: Divisor 2, Frequency 66669411 Hz Timecounter "TSC" frequency 2133421199 Hz quality -100 Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached hptrr: no controller detected. usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 usbus3: 12Mbps Full Speed USB v1.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 12Mbps Full Speed USB v1.0 usbus6: 12Mbps Full Speed USB v1.0 usbus7: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 ugen4.1: at usbus4 uhub4: on usbus4 ugen5.1: at usbus5 uhub5: on usbus5 ugen6.1: at usbus6 uhub6: on usbus6 ugen7.1: at usbus7 uhub7: on usbus7 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 2 ports with 2 removable, self powered uhub5: 2 ports with 2 removable, self powered uhub6: 2 ports with 2 removable, self powered mps0: SAS Device Page 0 : Slot: 8 EnclosureHandle: 0x1 SASAddress: 0x5942b0b0558ac200 ParentDevHandle: 0x1 PhyNum: 8 AccessStatus: 0x0 DevHandle: 0x9 AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: 4801,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 0 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 Expander found at enclosure 2 mps0: SAS Device Page 0 : Slot: 0 EnclosureHandle: 0x2 SASAddress: 0x500065b36789abff ParentDevHandle: 0x1 PhyNum: 0 AccessStatus: 0x0 DevHandle: 0xa AttachedPhyIdentifier: 0x13 ZoneGroup: 0 DeviceInfo: 1902,Edge Expander Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 8 DeviceName: 0xb3650050ffab8967 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 0 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c4f7d2d ParentDevHandle: 0xa PhyNum: 2 AccessStatus: 0x0 DevHandle: 0xb AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 4 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c4f6ec1 ParentDevHandle: 0xa PhyNum: 3 AccessStatus: 0x0 DevHandle: 0xc AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 5 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c4f7425 ParentDevHandle: 0xa PhyNum: 4 AccessStatus: 0x0 DevHandle: 0xd AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 1 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c4f7875 ParentDevHandle: 0xa PhyNum: 5 AccessStatus: 0x0 DevHandle: 0xe AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 2 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c54578d ParentDevHandle: 0xa PhyNum: 6 AccessStatus: 0x0 DevHandle: 0xf AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 3 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c545701 ParentDevHandle: 0xa PhyNum: 7 AccessStatus: 0x0 DevHandle: 0x10 AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 7 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c5454bd ParentDevHandle: 0xa PhyNum: 10 AccessStatus: 0x0 DevHandle: 0x11 AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 6 EnclosureHandle: 0x2 SASAddress: 0x5000c5002c4f5561 ParentDevHandle: 0xa PhyNum: 16 AccessStatus: 0x0 DevHandle: 0x12 AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: c01,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS Device Page 0 : Slot: 24 EnclosureHandle: 0x2 SASAddress: 0x500065b36789abfd ParentDevHandle: 0xa PhyNum: 24 AccessStatus: 0x0 DevHandle: 0x13 AttachedPhyIdentifier: 0x0 ZoneGroup: 0 DeviceInfo: 4c41,End Device Flags: 0x1 PhysicalPort: 0 MaxPortConnections: 1 DeviceName: 0x0 PortGroups: 4 DmaGroup: 0 ControlGroup: 4 mps0: SAS PHY Page 0 : OwnerDevHandle: 0x0001 AttachedDevHandle: 0x000a AttachedPhyIdentifier: 19 AttachedPhyInfo Reason: Loss DWORD Sync (0x14) ProgrammedLinkRate: 6.0Gbps (0xa8) HwLinkRate: 6.0Gbps (0xa8) ChangeCount: 1 Flags: 0x1 PhyInfo Reason: Power On (0x10000) NegotiatedLinkRate: 6.0Gbps (0xaa) mps0: Found device <1902,Edge Expander> <6.0Gbps> = <0x000a> <2/0> mps0: Triggering rescan of 0:0:-1 mps0: SAS PHY Page 0 : OwnerDevHandle: 0x0001 AttachedDevHandle: 0x000a AttachedPhyIdentifier: 21 AttachedPhyInfo Reason: Loss DWORD Sync (0x14) ProgrammedLinkRate: 6.0Gbps (0xa8) HwLinkRate: 6.0Gbps (0xa8) ChangeCount: 1 Flags: 0x1 PhyInfo Reason: Power On (0x10000) NegotiatedLinkRate: 6.0Gbps (0xaa) mps0: Found device ,End Device> <6.0Gbps> <0x000b> = <2/0> mps0: Triggering rescan of 0:1:-1 mps0: SAS PHY Page 0 : OwnerDevHandle: 0x0001 AttachedDevHandle: 0x000a AttachedPhyIdentifier: 20 AttachedPhyInfo Reason: Loss DWORD Sync (0x14) ProgrammedLinkRate: 6.0Gbps (0xa8) HwLinkRate: 6.0Gbps (0xa8) ChangeCount: 1 Flags: 0x1 PhyInfo Reason: Power On (0x10000) NegotiatedLinkRate: 6.0Gbps (0xaa) mps0: Found device ,End Device> <6.0Gbps> <0x000c> = <2/4> mps0: Triggering rescan of 0:4:-1 mps0: SAS PHY Page 0 : OwnerDevHandle: 0x0001 AttachedDevHandle: 0x000a AttachedPhyIdentifier: 15 AttachedPhyInfo Reason: Loss DWORD Sync (0x14) ProgrammedLinkRate: 6.0Gbps (0xa8) HwLinkRate: 6.0Gbps (0xa8) ChangeCount: 1 Flags: 0x1 PhyInfo Reason: Power On (0x10000) NegotiatedLinkRate: 6.0Gbps (0xaa) mps0: Found device ,End Device> <6.0Gbps> <0x000d> = <2/5> mps0: Triggering rescan of 0:5:-1 mps0: SAS PHY Page 0 : OwnerDevHandle: 0x0001 AttachedDevHandle: 0x000a AttachedPhyIdentifier: 14 AttachedPhyInfo Reason: Loss DWORD Sync (0x14) ProgrammedLinkRate: 6.0Gbps (0xa8) HwLinkRate: 6.0Gbps (0xa8) ChangeCount: 1 Flags: 0x1 PhyInfo Reason: Power On (0x10000) NegotiatedLinkRate: 6.0Gbps (0xaa) mps0: Found device ,End Device> <6.0Gbps> <0x000e> = <2/1> mps0: Triggering rescan of 0:2:-1 mps0: SAS PHY Page 0 : OwnerDevHandle: 0x0001 AttachedDevHandle: 0x000a AttachedPhyIdentifier: 13 AttachedPhyInfo Reason: Loss DWORD Sync (0x14) ProgrammedLinkRate: 6.0Gbps (0xa8) HwLinkRate: 6.0Gbps (0xa8) ChangeCount: 1 Flags: 0x1 PhyInfo Reason: Power On (0x10000) NegotiatedLinkRate: 6.0Gbps (0xaa) mps0: Found device ,End Device> <6.0Gbps> <0x000f> = <2/2> mps0: Triggering rescan of 0:3:-1 mps0: SAS PHY Page 0 : OwnerDevHandle: 0x0001 AttachedDevHandle: 0x000a AttachedPhyIdentifier: 12 AttachedPhyInfo Reason: Loss DWORD Sync (0x14) ProgrammedLinkRate: 6.0Gbps (0xa8) HwLinkRate: 6.0Gbps (0xa8) ChangeCount: 1 Flags: 0x1 PhyInfo Reason: Power On (0x10000) NegotiatedLinkRate: 6.0Gbps (0xaa) mps0: Found device ,End Device> <6.0Gbps> <0x0010> = <2/3> mps0: Triggering rescan of 0:6:-1 uhub2: 4 ports with 4 removable, self powered uhub7: 4 ports with 4 removable, self powered mps0: mpssas_discovery_end: removing confighook ugen2.2: at usbus2 uhub8: = on usbus2 ugen7.2: at usbus7 umass0: on = usbus7 umass0: SCSI over Bulk-Only; quirks =3D 0x4101 uhub8: 4 ports with 4 removable, self powered umass0:1:0:-1: Attached to scbus1 mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 (probe0:mps0:0:0:0): Error 22, Unretryable error (probe0:mps0:0:0:0): Down reving Protocol Version from 4 to 2? mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 (probe0:mps0:0:0:0): Error 22, Unretryable error (probe0:mps0:0:0:0): Down reving Protocol Version from 4 to 2? mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 (probe0:mps0:0:0:0): Error 22, Unretryable error (probe0:mps0:0:0:0): Down reving Protocol Version from 4 to 2?ugen2.3: = at usbus2 mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 (probe0:mps0:0:0:0): Error 22, Unretryable error (probe0:mps0:0:0:0): Down reving Protocol Version from 4 to 2? mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc ukbd0: on usbus2 (probe0:mps0:0:0:0): Error 22, Unretryable error (probe0:mps0:0:0:0): Down reving Protocol Version from 4 to 2? mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 (probe0:mps0:0:0:0): Error 22, Unretryable error (probe0:mps0:0:0:0): Down reving Protocol Version from 4 to 2? mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 (probe0:mps0:0:0:0): Error 22, Unretryable errorkbd2 at ukbd0 kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000 (probe0:mps0:0:0:0): Down reving Protocol Version from 4 to 2? mps0: (0:0:0) IOCStatus=3D 0x43, ScsiStatus=3D 0x0, SCSIState=3D 0x4 = TransferCount=3D 0x0 (probe0:mps0:0:0:0): Error 22, Unretryable error mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0x11 mps0: (0:4:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:1:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:3:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:2:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:5:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc mps0: (0:6:0) IOCStatus=3D 0x45, ScsiStatus=3D 0x0, SCSIState=3D 0x0 = TransferCount=3D 0xc pass0 at mps0 bus 0 scbus0 target 1 lun 0 pass0: Fixed Direct Access SCSI-5 device=20 pass0: Serial Number 6SJ0642S pass0: 600.000MB/s transfers pass0: Command Queueing enabled pass1 at mps0 bus 0 scbus0 target 2 lun 0 pass1: Fixed Direct Access SCSI-5 device=20 pass1: Serial Number 6SJ06F4Z pass1: 600.000MB/s transfers pass1: Command Queueing enabled pass2 at mps0 bus 0 scbus0 target 3 lun 0 pass2: Fixed Direct Access SCSI-5 device=20 pass2: Serial Number 6SJ07AMF pass2: 600.000MB/s transfers pass2: Command Queueing enabled pass3 at mps0 bus 0 scbus0 target 4 lun 0 pass3: Fixed Direct Access SCSI-5 device=20 pass3: Serial Number 6SJ06T5C pass3: 600.000MB/s transfers pass3: Command Queueing enabled pass4 at mps0 bus 0 scbus0 target 5 lun 0 pass4: Fixed Direct Access SCSI-5 device=20 pass4: Serial Number 6SJ06T75 pass4: 600.000MB/s transfers pass4: Command Queueing enabled pass5 at mps0 bus 0 scbus0 target 6 lun 0 pass5: Fixed Direct Access SCSI-5 device=20 pass5: Serial Number 6SJ07AP9 pass5: 600.000MB/s transfers pass5: Command Queueing enabled pass6 at umass-sim0 bus 0 scbus1 target 0 lun 0 pass6: Removable Direct Access SCSI-2 device=20 pass6: Serial Number 09FE0AAE pass6: 40.000MB/s transfers da0 at mps0 bus 0 scbus0 target 1 lun 0 da0: Fixed Direct Access SCSI-5 device=20 da0: Serial Number 6SJ0642S da0: 600.000MB/s transfers da0: Command Queueing enabled da0: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) da1 at mps0 bus 0 scbus0 target 2 lun 0 da1: Fixed Direct Access SCSI-5 device=20 da1: Serial Number 6SJ06F4Z da1: 600.000MB/s transfers da1: Command Queueing enabled da1: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) da2 at mps0 bus 0 scbus0 target 3 lun 0 da2: Fixed Direct Access SCSI-5 device=20 da2: Serial Number 6SJ07AMF da2: 600.000MB/s transfers da2: Command Queueing enabled da2: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) GEOM: new disk da0 GEOM: new disk da1 GEOM: new disk da2 da3 at mps0 bus 0 scbus0 target 4 lun 0 da3: Fixed Direct Access SCSI-5 device=20 da3: Serial Number 6SJ06T5C da3: 600.000MB/s transfers da3: Command Queueing enabled da3: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) da4 at mps0 bus 0 scbus0 target 5 lun 0 da4: Fixed Direct Access SCSI-5 device=20 da4: Serial Number 6SJ06T75 da4: 600.000MB/s transfers da4: Command Queueing enabled da4: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) da5 at mps0 bus 0 scbus0 target 6 lun 0 da5: Fixed Direct Access SCSI-5 device=20 da5: Serial Number 6SJ07AP9 da5: 600.000MB/s transfers da5: Command Queueing enabled da5: 140014MB (286749480 512 byte sectors: 255H 63S/T 17849C) (da6:umass-sim0:0:0:0): SCSI status error (da6:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0=20 (da6:umass-sim0:0:0:0): CAM status: SCSI Status Error (da6:umass-sim0:0:0:0): SCSI status: Check Condition (da6:umass-sim0:0:0:0): SCSI sense: UNIT ATTENTION asc:28,0 (Not ready = to ready change, medium may have changed) (da6:umass-sim0:0:0:0): Retrying command (per sense data) da6 at umass-sim0 bus 0 scbus1 target 0 lun 0 da6: Removable Direct Access SCSI-2 device=20 da6: Serial Number 09FE0AAE da6: 40.000MB/s transfers da6: 976MB (1998848 512 byte sectors: 64H 32S/T 976C) GEOM: new disk da3 GEOM: new disk da4 GEOM: new disk da5 GEOM: new disk da6 ATA PseudoRAID loaded llaappiicc3354:: CCMMCCII = uunnmmaasskkededlllalaaappppiiiciccc550515:3:2 :: C CCMCMCMCCIMII C = uIun nmuumansnmkmaeadassskkeedkded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x21000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000100f2 SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x22000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 SMP: AP CPU #4 Launched! cpu4 AP: ID: 0x32000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x23000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 SMP: AP CPU #6 Launched! cpu6 AP: ID: 0x34000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 SMP: AP CPU #5 Launched! cpu5 AP: ID: 0x33000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 SMP: AP CPU #7 Launched! cpu7 AP: ID: 0x35000000 VER: 0x01060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 cmci: 0x000000f2 ioapic0: routing intpin 3 (ISA IRQ 3) to lapic 33 vector 48 ioapic0: routing intpin 4 (ISA IRQ 4) to lapic 34 vector 48 ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 35 vector 48 ioapic0: routing intpin 17 (PCI IRQ 17) to lapic 50 vector 48 ioapic0: routing intpin 18 (PCI IRQ 18) to lapic 51 vector 48 ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 52 vector 48 ioapic0: routing intpin 20 (PCI IRQ 20) to lapic 53 vector 48 msi: Assigning MSI IRQ 256 to local APIC 33 vector 49 msi: Assigning MSI IRQ 257 to local APIC 34 vector 49 msi: Assigning MSI-X IRQ 258 to local APIC 35 vector 49 Trying to mount root from ufs:/dev/da8s1a ROOT MOUNT ERROR:=20 If you have invalid mount options, reboot, and first try the following = from the loader prompt: set vfs.root.mountfrom.options=3Drw and then remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom=3Dufs:/dev/da8s1a vfs.root.mountfrom.options=3D Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a eg. cd9660:/dev/acd0 This is equivalent to: mount -t cd9660 /dev/acd0 = / ? List valid disk boot devices Abort manual input mountroot> ufs:/dewv/\^H \^H\^H \^H\^H \^Hv/da6s1a Trying to mount root from ufs:/dev/da6s1a WARNING: / was not properly dismounted ct_to_ts([2011-01-26 10:58:35]) =3D 1296039515.000000000 start_init: trying /sbin/init WARNING: / was not properly dismounted #=20 From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 26 14:12:21 2011 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 08A731065675 for ; Wed, 26 Jan 2011 14:12:21 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id C576C8FC1A for ; Wed, 26 Jan 2011 14:12:20 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.messagingengine.com (Postfix) with ESMTP id B02C52075B; Wed, 26 Jan 2011 09:12:19 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 26 Jan 2011 09:12:19 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:to:subject:date:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; s=smtpout; bh=Ww9TtvJwpX9+s2wJFoLbreCjBiY=; b=ZZyotfSbiPKCDyCbyMRDeGorm7Zww+4SPoxoxkkVl531Y4B8mgLGZ7R/LroFXevvRz43BGVLZsdR5y2g1a9R1D0+DZUwDPjwEtjuVogprIolyFyMQGfh+edGz/qHTrwsb6K7Re+4SJHc4GC+07yI+Cqx4AgB54M8KEOSbNtxtO4= X-Sasl-enc: lhm+2AwDKXG2SECxP7iOKFKuvUfKfPIoKff63roQu+QN 1296051139 Received: from tcbug.ixsystems.com (74-34-19-98.dr01.rsmt.mn.frontiernet.net [74.34.19.98]) by mail.messagingengine.com (Postfix) with ESMTPSA id 4CA46441952; Wed, 26 Jan 2011 09:12:19 -0500 (EST) From: Josh Paetzel To: freebsd-scsi@freebsd.org Date: Wed, 26 Jan 2011 08:12:11 -0600 User-Agent: KMail/1.13.5 (FreeBSD/8.1-RELEASE; KDE/4.4.5; amd64; ; ) References: <522B2387-1BE2-4AF7-B250-B1272D301C59@sarenet.es> <18831097-9113-4059-BAEB-71185849BD90@sarenet.es> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart12003889.O776zbyQj6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201101260812.17434.josh@tcbug.org> Cc: Peter Lai Subject: Re: ZFS and "internal" mfi RAID cards, the eternal question 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: Wed, 26 Jan 2011 14:12:21 -0000 --nextPart12003889.O776zbyQj6 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Friday, January 14, 2011 08:03:01 am Peter Lai wrote: > On Fri, Jan 14, 2011 at 6:44 AM, Borja Marcos wrote: > > On Jan 14, 2011, at 12:50 PM, Peter Lai wrote: > >> Is there a reason you are ordering your Dells with H700 instead of > >> H200; do you really want the battery backed cache anyway? > >> http://www.dell.com/content/topics/topic.aspx/global/products/pvaul/to= pi > >> cs/en/us/raid_controller?c=3Dus&l=3Den&cs=3D555 suggests the H200 has = jbod > >> mode... > >=20 > > Indeed, it doesn't work under FreeBSD. Or am I wrong? >=20 > Good point. My guess here is that as an LSI card, it's not really > supposed be picked up by mfi, but mpt. But most of my experience with > dell has been to not even bother with the addon raid and just stick > with the mpt controllers. Of course, they only support up to 8 disks, > so if you need more than that...well :( The H200 is a 6 gbps LSI SAS HBA under the hood that is not supported by mp= t. =20 There is a new driver in HEAD called mps that supports the card. People ha= ve=20 had varying amounts of success running the driver ported to 8.x. I can=20 provide you with a .ko that works on 8.x, but it comes with a YMMV warranty. =46WIW, this driver won't be appearing in 8.2 due to various concerns the p= eople=20 working on it had with it. =2D-=20 Thanks, Josh Paetzel --nextPart12003889.O776zbyQj6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iQEcBAABAgAGBQJNQCvBAAoJEKFq1/n1feG2oHQH/0uAiwZBywRJOdzzc9lFckva uXuPMemjl4/AXLRagwiSrmXfbwv64I61jGAAbpT2YjV/WFgAVTIPCuEjjo22sw8K VoXks9kodonfyFsvFjqy1YB88IN8NfCR95aU4rT8CAozfgg2L/mJ0RAce9nAMNAU aarp1zC4Fhbxd3T22eYdswhoDD7O02JlqUti2zAiJu/Hydm3v5ATi8eiXRWrx9iK 3Rk+b4BbQ5S67oI1iFpQp+4AtTbTEFKr1c31JPyr5IwCqd9d41tewbXuzMHPMITU AhdMnlrsJaj4yDLLGuxsHfV07gYRFi1dSCc9Cg6gpdTrm8d77/OPZH30fAclp48= =j3q/ -----END PGP SIGNATURE----- --nextPart12003889.O776zbyQj6-- From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 26 14:19:54 2011 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 C52E61065696 for ; Wed, 26 Jan 2011 14:19:54 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop1b.sarenet.es (proxypop1b.sarenet.es [194.30.0.104]) by mx1.freebsd.org (Postfix) with ESMTP id 8432A8FC15 for ; Wed, 26 Jan 2011 14:19:54 +0000 (UTC) Received: from [172.16.1.55] (ssglan.sare.net [192.148.167.100]) by proxypop1b.sarenet.es (Postfix) with ESMTP id 81C966077; Wed, 26 Jan 2011 15:19:52 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=iso-8859-1 From: Borja Marcos In-Reply-To: <201101260812.17434.josh@tcbug.org> Date: Wed, 26 Jan 2011 15:19:52 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <482769AA-B8E1-4C11-B737-7F918650FAEF@sarenet.es> References: <522B2387-1BE2-4AF7-B250-B1272D301C59@sarenet.es> <18831097-9113-4059-BAEB-71185849BD90@sarenet.es> <201101260812.17434.josh@tcbug.org> To: Josh Paetzel X-Mailer: Apple Mail (2.1082) Cc: freebsd-scsi@freebsd.org, Peter Lai Subject: Re: ZFS and "internal" mfi RAID cards, the eternal question 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: Wed, 26 Jan 2011 14:19:54 -0000 On Jan 26, 2011, at 3:12 PM, Josh Paetzel wrote: > On Friday, January 14, 2011 08:03:01 am Peter Lai wrote: >> On Fri, Jan 14, 2011 at 6:44 AM, Borja Marcos = wrote: >>> On Jan 14, 2011, at 12:50 PM, Peter Lai wrote: >>>> Is there a reason you are ordering your Dells with H700 instead of >>>> H200; do you really want the battery backed cache anyway? >>>> = http://www.dell.com/content/topics/topic.aspx/global/products/pvaul/topi >>>> cs/en/us/raid_controller?c=3Dus&l=3Den&cs=3D555 suggests the H200 = has jbod >>>> mode... >>>=20 >>> Indeed, it doesn't work under FreeBSD. Or am I wrong? >>=20 >> Good point. My guess here is that as an LSI card, it's not really >> supposed be picked up by mfi, but mpt. But most of my experience with >> dell has been to not even bother with the addon raid and just stick >> with the mpt controllers. Of course, they only support up to 8 = disks, >> so if you need more than that...well :( >=20 > The H200 is a 6 gbps LSI SAS HBA under the hood that is not supported = by mpt. =20 > There is a new driver in HEAD called mps that supports the card. = People have=20 > had varying amounts of success running the driver ported to 8.x. I = can=20 > provide you with a .ko that works on 8.x, but it comes with a YMMV = warranty. >=20 > FWIW, this driver won't be appearing in 8.2 due to various concerns = the people=20 > working on it had with it. Thanks :) I've been using it (moving it from 9-CURRENT to 8-STABLE is very easy) = and except for a couple of problems (see my posting in this same list) = it's working great. I really look forward to see a production ready version. I'm really = annoyed by the =FCber crappy "mfi=A8 cards. Borja. From owner-freebsd-scsi@FreeBSD.ORG Wed Jan 26 23:07:11 2011 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 D62641065672 for ; Wed, 26 Jan 2011 23:07:11 +0000 (UTC) (envelope-from david.tidey@tidey.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 98C928FC16 for ; Wed, 26 Jan 2011 23:07:11 +0000 (UTC) Received: by qyk36 with SMTP id 36so1468206qyk.13 for ; Wed, 26 Jan 2011 15:07:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.229.68 with SMTP id jh4mr852289qcb.103.1296081339543; Wed, 26 Jan 2011 14:35:39 -0800 (PST) Received: by 10.229.222.141 with HTTP; Wed, 26 Jan 2011 14:35:39 -0800 (PST) Date: Wed, 26 Jan 2011 22:35:39 +0000 Message-ID: From: David Tidey To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: istgt performance issue when copying large files (1G plus) 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: Wed, 26 Jan 2011 23:07:11 -0000 Hello, I am using FreeBSD 8.2 with the very latest istgt version 20110103. I am using istgt to expose a zfs volume to a windows client. When running a disk benchmark which writes 10 files of around 40mb each performance is 60-70Mb/sec. When I copy a video file over over 1G performance starts off fast - 60Mb/sec plus. After copying a couple of 100Mb performance starts to drop to less than 10Mb/sec. Exposing the same disks using samba gives performance of 40-50Mb/sec with no drop off problems I therefore am assuming this is an istgt problem Any views on how to diagnose this? David