From owner-freebsd-scsi@FreeBSD.ORG Fri Feb 17 08:01:20 2012 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 3E42C1065670 for ; Fri, 17 Feb 2012 08:01:20 +0000 (UTC) (envelope-from nitroboost@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id F3B088FC16 for ; Fri, 17 Feb 2012 08:01:19 +0000 (UTC) Received: by obcwo16 with SMTP id wo16so5300807obc.13 for ; Fri, 17 Feb 2012 00:01:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jcipJ1S54qy24eNTewoUfKxvamDCwAyS+3vRlEDHMsk=; b=KFZYpA61v0pfRVN3WaZYhM6IrjPFZX5rBfeHNudS4EAmtZo2w5N7MBSXQl96HaPvpx VMPrfqNMfQGuVyl2h3khRpgOhWlYD656230pGrbGswgjI4+XUO63G2b3J6xv2sJ4p2FT 2q57dC8c4OHVc1acK9JrYdbzgLrqHfFivjHPw= MIME-Version: 1.0 Received: by 10.182.231.100 with SMTP id tf4mr4267567obc.56.1329465679334; Fri, 17 Feb 2012 00:01:19 -0800 (PST) Received: by 10.182.225.100 with HTTP; Fri, 17 Feb 2012 00:01:19 -0800 (PST) In-Reply-To: References: Date: Fri, 17 Feb 2012 01:01:19 -0700 Message-ID: From: Jason Wolfe To: "Desai, Kashyap" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-scsi@freebsd.org" Subject: Re: LSI2008 controller clobbers first disk with new LSI mps driver 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, 17 Feb 2012 08:01:20 -0000 Kashyap, Ah a response from LSI, that's a pleasant surprise :) Everything you've stated looks correct to me, the FreeBSD developed driver that has been replaced by the LSI driver has no issues with either firmware. Your likely aware, but just to confirm, here is the history of the 3 various LSI drivers that have the issue on the 10.00.02.00 FW: 11.00.00.00 - binary driver I had received from you guys in mid 2011, mpslsi.ko, one for each 7.2-RELEASE and 8.2-RELEASE 11.255.03.00-fbsd - initial LSI driver committed to 8-STABLE on 2/2, r230922 13.00.00.00-fbsd - commited to 8-STABLE on 2/14, r231680 I have about 40 boxes with the 10.00.02.00 FW I've tested, so I'm fairly certain it's not bad hardware or a fluke. You guys haven't seen anything like this in house? I'd hate to hear I have to update the FW on these boxes as they are all quite a ways from me, though it seems there is some way to work around the behavior in the driver as the FreeBSD one does? I have a few of these boxes out of service so I'm game to try some things out should that help. Thank for the response, Jason On Thu, Feb 16, 2012 at 11:29 PM, Desai, Kashyap wrote: > Jason, > > I have gone through your data provided in this thread. It is well > understood because of your descriptive data. > > So What I understood here is: > > 1. You tested with HBA Fw "07.00.00.00" and "10.00.02.00" > > 2. you have run your test on two different LSI BIOS versions. > Grabbed from below line. > MPT2BIOS-7.11.00.00 (2010.07.29) / PRODUCT REVISION 7.00.00.00 > MPT2BIOS-7.19.00.00 (2011.05.16) / PRODUCT REVISION 10.00.02.00 > > > Now I am able to see below three difference in your setup. > > See FW version and check starting target id, all three has different way > of assigning TargetIDs. > For first two case target id start with "8" but SES device assignment is > different. > Last case target id start with "1" > > > mps0: Firmware: 07.00.00.00, Driver: 11.255.03.00-fbsd (OR) > 13.00.00.00-fbsd > > > at scbus0 target 8 lun 0 (pass0,da0) > > > at scbus0 target 9 lun 0 (pass1,da1) > > > at scbus0 target 10 lun 0 (pass2,da2) > > > at scbus0 target 11 lun 0 (pass3,da3) > > > at scbus0 target 12 lun 0 (pass4,da4) > > > at scbus0 target 13 lun 0 (pass5,da5) > > > at scbus0 target 14 lun 0 (pass6,da6) > > > at scbus0 target 15 lun 0 (pass7,da7) > > > at scbus0 target 16 lun 0 (pass8,da8) > > > at scbus0 target 17 lun 0 (pass9,da9) > > > at scbus0 target 18 lun 0 (pass10,da10) > > > at scbus0 target 19 lun 0 (pass11,da11) > > > at scbus0 target 20 lun 0 (ses0,pass12) > > mps0: Firmware: 10.00.02.00, Driver: 13.00.00.00-fbsd > mps0: Firmware: 10.00.02.00, Driver: 11.00.00.00 (OR) 8.2-STABLE Inbox > > > at scbus0 target 8 lun 0 (ses0,pass0) > > > at scbus0 target 9 lun 0 (da0,pass1) > > > at scbus0 target 10 lun 0 (da1,pass2) > > > at scbus0 target 11 lun 0 (da2,pass3) > > > at scbus0 target 12 lun 0 (da3,pass4) > > > at scbus0 target 13 lun 0 (da4,pass5) > > > at scbus0 target 14 lun 0 (da5,pass6) > > > at scbus0 target 15 lun 0 (da6,pass7) > > > at scbus0 target 16 lun 0 (da7,pass8) > > > at scbus0 target 17 lun 0 (da8,pass9) > > > at scbus0 target 18 lun 0 (da9,pass10) > > > at scbus0 target 19 lun 0 (da10,pass11) > > On the FBSD developed driver active in 8-STABLE prior to the LSI > Release (Firmware: 10.00.02.00) > > > > at scbus0 target 1 lun 0 (pass0,da0) > > > at scbus0 target 2 lun 0 (pass1,da1) > > > at scbus0 target 3 lun 0 (pass2,da2) > > > at scbus0 target 4 lun 0 (pass3,da3) > > > at scbus0 target 5 lun 0 (pass4,da4) > > > at scbus0 target 6 lun 0 (pass5,da5) > > > at scbus0 target 7 lun 0 (pass6,da6) > > > at scbus0 target 8 lun 0 (pass7,da7) > > > at scbus0 target 9 lun 0 (pass8,da8) > > > at scbus0 target 10 lun 0 (pass9,da9) > > > at scbus0 target 11 lun 0 (pass10,da10) > > > at scbus0 target 12 lun 0 (pass11,da11) > > > at scbus0 target 13 lun 0 (ses0,pass12) > > > > In summary, (please confirm) > 1. you have not seen any issue if you use "07.00.00.00" FW version. > 2. _but_ when you use "10.00.02.00" FW, with "13.00.00.00-fbsd" driver > version you are seeing > SES is detected before Drives as pass0. > 3. When you use "10.00.02.00" FW with 8-STABLE inbox FBSD driver, you are > finding SES device detected after Drives. > > > All driver is doing here is asking CAM layer to scan Bus when there is any > device added on that bus. > So depending upon actual target Id assigned by FW, it will be detected to > camcontrol. > > So bottom line is FW plays major role in sequencing Drives behind LSI > controller. > > ~ Kashyap >