From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 22 15:20:37 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 14551106566B for ; Wed, 22 Feb 2012 15:20:37 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog111.obsmtp.com (na3sys009aog111.obsmtp.com [74.125.149.205]) by mx1.freebsd.org (Postfix) with ESMTP id 700648FC1F for ; Wed, 22 Feb 2012 15:20:36 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob111.postini.com ([74.125.148.12]) with SMTP ID DSNKT0UHw/UpCBld+X2wXrE526Ms+CLK9OND@postini.com; Wed, 22 Feb 2012 07:20:36 PST Received: from PALCAS01.lsi.com (128.94.213.117) by PALEDGE01.lsi.com (192.19.193.42) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 22 Feb 2012 10:25:22 -0500 Received: from inbexch01.lsi.com (135.36.98.37) by PALCAS01.lsi.com (128.94.213.117) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 22 Feb 2012 10:20:34 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch01.lsi.com ([135.36.98.37]) with mapi; Wed, 22 Feb 2012 20:50:31 +0530 From: "Desai, Kashyap" To: Jason Wolfe Date: Wed, 22 Feb 2012 20:50:30 +0530 Thread-Topic: LSI2008 controller clobbers first disk with new LSI mps driver Thread-Index: AczxdG6PnOp+UMIBRRyXElGdqyWDowAAIYHA Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-scsi@freebsd.org" , "McConnell, Stephen" 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: Wed, 22 Feb 2012 15:20:37 -0000 Jason, You may need to set Enclosure settings properly. See below prints. LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f5cdb5 slot 0 =09 LSI Debug _mapping_get_dev_info 982 8 13 255 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49c01 slot 1=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f6c799 slot 2=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033e562f5 slot 3=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49a41 slot 4=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f5efe9 slot 5=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49a11 slot 6=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49c71 slot 7=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f40fb1 slot 8=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f6cba9 slot 9=20 .....=20 mps0: (13)->(mpssas_fw_work) Event Free: [1c] mps0: (13)->(mpssas_fw_work) Working on Event: [1c] LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f650cd slot 10=20 LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f29109 slot 11=20 LSI Debug _mapping_get_dev_info 946 sas addr 500304800126e3fd slot 0 < -- = SES is on slot-0 and even your first drive is also on slot-0 This is a problem. I hope you can rectify from enclosure settings and don't need further help = from driver side. ~ Kashyap > -----Original Message----- > From: Jason Wolfe [mailto:nitroboost@gmail.com] > Sent: Wednesday, February 22, 2012 8:43 PM > To: Desai, Kashyap > Cc: freebsd-scsi@freebsd.org; McConnell, Stephen > Subject: Re: LSI2008 controller clobbers first disk with new LSI mps > driver >=20 > On Wed, Feb 22, 2012 at 1:39 AM, Desai, Kashyap > wrote: > > Here is a possible root cause of this issue. > > > > Enclosure which you are using in your setup (might be) not configured > properly. > > > > You have Enclosure with 12 Slots + 1 SES Device. > > See below detail from the log. > > > > =A0 =A0 =A0 =A0EventDataLength: 5 > > =A0 =A0 =A0 =A0AckRequired: 0 > > =A0 =A0 =A0 =A0Event: SasEnclDeviceStatusChange (0x1d) > > =A0 =A0 =A0 =A0EventContext: 0x0 > > =A0 =A0 =A0 =A0EnclosureHandle: 0x2 > > =A0 =A0 =A0 =A0ReasonCode: Added > > =A0 =A0 =A0 =A0PhysicalPort: 0 > > =A0 =A0 =A0 =A0NumSlots: 13 > > =A0 =A0 =A0 =A0StartSlot: 0 > > =A0 =A0 =A0 =A0PhyBits: 0xff > > > > StartSlot is 0 in this case. > > Correct behavior should be each device on your enclosure must have > different slot number starting from 0 till 12. > > I have doubt that SES device has not configured well and it is using > slot-0 as default. This can create issue for actual device which is > connected to slot-0. > > So In your setup you will have slot-0 till slot-11 assigned for actual > Phys of your enclosures and again slot-0 is assigned for SES device > instead of Slot-12. > > > > To confirm my doubt: please provide me debug dmesg log using attached > patch. > > > > ~ Kashyap >=20 > Is the SES device a component of the LSI2008 controller, or is it a > separate piece? In either case, the device would have come configured > this way from LSI/Supermicro as we have not touched the configs. If > this is something we can't resolve in the driver that won't be much fun > :) >=20 > On Wed, Feb 22, 2012 at 3:35 AM, Desai, Kashyap > wrote: > > Ignore " dump_mapping_svn_2.patch" (it is wrong patch file) > > > > Attached " dump_mapping_svn_3.patch". > > > > ` Kashyap >=20 > Attached is the boot log with the dump_mapping_svn_3.patch applied >=20 > Jason