From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 22 15:39:25 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 CB225106566C for ; Wed, 22 Feb 2012 15:39:25 +0000 (UTC) (envelope-from Kashyap.Desai@lsi.com) Received: from na3sys009aog101.obsmtp.com (na3sys009aog101.obsmtp.com [74.125.149.67]) by mx1.freebsd.org (Postfix) with ESMTP id 3B69B8FC0A for ; Wed, 22 Feb 2012 15:39:24 +0000 (UTC) Received: from paledge01.lsi.com ([192.19.193.42]) (using TLSv1) by na3sys009aob101.postini.com ([74.125.148.12]) with SMTP ID DSNKT0UMLM3OwV4JCLhErECXcNMWmKRGTGjc@postini.com; Wed, 22 Feb 2012 07:39:25 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:44:11 -0500 Received: from inbexch02.lsi.com (135.36.98.40) by PALCAS01.lsi.com (128.94.213.117) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 22 Feb 2012 10:39:23 -0500 Received: from inbmail01.lsi.com ([135.36.98.64]) by inbexch02.lsi.com ([135.36.98.40]) with mapi; Wed, 22 Feb 2012 21:09:20 +0530 From: "Desai, Kashyap" To: "dgilbert@interlog.com" Date: Wed, 22 Feb 2012 21:09:19 +0530 Thread-Topic: LSI2008 controller clobbers first disk with new LSI mps driver Thread-Index: Aczxd3MCM9SpXIb4SqyvNbVaqLw/iwAAFdaQ Message-ID: References: <4F450AF3.3020300@interlog.com> In-Reply-To: <4F450AF3.3020300@interlog.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" 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:39:25 -0000 > -----Original Message----- > From: Douglas Gilbert [mailto:dgilbert@interlog.com] > Sent: Wednesday, February 22, 2012 9:04 PM > To: Desai, Kashyap > Cc: Jason Wolfe; freebsd-scsi@freebsd.org; McConnell, Stephen > Subject: Re: LSI2008 controller clobbers first disk with new LSI mps > driver >=20 > On 12-02-22 10:20 AM, Desai, Kashyap wrote: > > Jason, > > > > You may need to set Enclosure settings properly. > > > > See below prints. > > > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f5cdb5 slot 0 >=20 > > LSI Debug _mapping_get_dev_info 982 8 13 255 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49c01 slot 1 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f6c799 slot 2 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033e562f5 slot 3 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49a41 slot 4 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f5efe9 slot 5 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49a11 slot 6 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f49c71 slot 7 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f40fb1 slot 8 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f6cba9 slot 9 > > ..... > > 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 > > LSI Debug _mapping_get_dev_info 946 sas addr 5000c50033f29109 slot 11 > > 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. >=20 > Again, no. Forget the slot numbers, look at the expander phy id. > Slot numbers are mickey mouse, don't trust them for device > discovery. As I suggested in my previous post, expander virtual > phys don't have slot numbers, so the value you read is > effectively "don't care". >=20 > If this problem reported with FreeBSD happened with Linux, > I (and a lot of others) would have been yelling at anyone > we could find in LSI. My first stop would be Eric Moore. Doug, Thanks for your input. I really need more clarity from architect from= LSI on this front. I don't recall why we choose slot as key for our mappin= g table search. BTW, Linux does not have this mapping mode support due to scsi transport la= yer. We have similar support for older Linux (RHEL4/SLES9) ~ Kashyap >=20 > Doug Gilbert >=20 > > 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 > >> > >> 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. > >>> > >>> EventDataLength: 5 > >>> AckRequired: 0 > >>> Event: SasEnclDeviceStatusChange (0x1d) > >>> EventContext: 0x0 > >>> EnclosureHandle: 0x2 > >>> ReasonCode: Added > >>> PhysicalPort: 0 > >>> NumSlots: 13 > >>> StartSlot: 0 > >>> PhyBits: 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 > >> > >> 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 > >> :) > >> > >> 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 > >> > >> Attached is the boot log with the dump_mapping_svn_3.patch applied > >> > >> Jason > > _______________________________________________ > > 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" > >