Date: Wed, 22 Feb 2012 21:09:19 +0530 From: "Desai, Kashyap" <Kashyap.Desai@lsi.com> To: "dgilbert@interlog.com" <dgilbert@interlog.com> Cc: "freebsd-scsi@freebsd.org" <freebsd-scsi@freebsd.org>, "McConnell, Stephen" <Stephen.McConnell@lsi.com> Subject: RE: LSI2008 controller clobbers first disk with new LSI mps driver Message-ID: <B2FD678A64EAAD45B089B123FDFC3ED72B96D3483C@inbmail01.lsi.com> In-Reply-To: <4F450AF3.3020300@interlog.com> References: <CAAAm0r2NFhF=eh2bOPMnVN8E6e2o0KfaST0N-M_gWoJHpFOLmQ@mail.gmail.com> <CAFPOs6pwb44oNabH5vabDPJyFutMKa5mhgvHY=HkQVpV20YiYw@mail.gmail.com> <CAAAm0r1pWN-F=madGdk7N%2BoRuZmSD5_MAYwLh6By126L0CTGuw@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D34558@inbmail01.lsi.com> <CAAAm0r1x15_ho2MD0tX7Y7A6mnU2N6zihNOz_Qz=jpsyBkDCWQ@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D3455B@inbmail01.lsi.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D34626@inbmail01.lsi.com> <CAAAm0r3_S2jTG=Te4UhLqHPqiXq7_aAOHNp=W3jb4KLJx9PTRg@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D34748@inbmail01.lsi.com> <CAAAm0r3oRTcfipyVcp9nE1CL3dcK7cft8AUSf%2BfGYVK90b2A0w@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D347BB@inbmail01.lsi.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D347ED@inbmail01.lsi.com> <CAAAm0r3kKP5weF9BRDvoKPiPxvt0=Y-hwepcC-OMyoXio8hrRw@mail.gmail.com> <B2FD678A64EAAD45B089B123FDFC3ED72B96D3483B@inbmail01.lsi.com> <4F450AF3.3020300@interlog.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----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<Kashyap.Desai@lsi.com> > >> 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<Kashyap.Desai@lsi.com> > >> 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" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B2FD678A64EAAD45B089B123FDFC3ED72B96D3483C>