Date: Thu, 14 Feb 2013 14:02:36 +0100 From: Harald Schmalzbauer <h.schmalzbauer@omnilan.de> To: Dennis Glatting <freebsd@pki2.com> Cc: freebsd-questions@freebsd.org Subject: Re: Problems with the LSI 9211-8i or LSI SAS2008 chips? Message-ID: <511CE06C.2080909@omnilan.de> In-Reply-To: <1350573079.3968.41.camel@btw.pki2.com> References: <1350573079.3968.41.camel@btw.pki2.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig13364FC05F68CABA07F4A624 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable schrieb Dennis Glatting am 18.10.2012 17:11 (localtime): > I am working with some folks on this list on a ZFS problem where I am > using LSI 9211-8i boards flashed to IT, which use the LSI SAS2008 chips= > (I own about ten of these boards). I have used various versions of BIOS= > and firmware from LSI in these boards and presently using LSI's most > recent. The 2008 chips are listed as supported in the driver and I have= > also used Supermicro boards with these chips. > > mps0: <LSI SAS2008> port 0xc000-0xc0ff mem > 0xfe93c000-0xfe93ffff,0xfe940000-0xfe97ffff irq 32 at device 0.0 on pci= 3 > mps0: Firmware: 14.00.00.00, Driver: 14.00.00.01-fbsd > mps0: IOCCapabilities: > 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDi= sc> > > In the debugging process the question arose related to chip revisions, > firmware revisions, and folks general opinion about the 9211-8i /or/ > recommendation of something better for a ZFS HBA. We /do not/ know if > the problem experienced is this board/chip/firmware, rather we're simpl= y > asking questions about them. > > Opinions? Experiences? I'm using exactly the same silicon for ZFS storage servers: mps0: <LSI SAS2008> port 0x5000-0x50ff mem 0xd6500000-0xd6503fff,0xd6540000-0xd657ffff irq 19 at device 0.0 on pci5 mps0: Firmware: 14.00.00.00, Driver: 14.00.00.01-fbsd mps0: IOCCapabilities: 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc= > No hardware related problems so far. Only annoying point is that MSI-X initialisation doesn't work with beeing a VT-d passthrough device into ESXi guest. I have to "hw.mps.disable_msix=3D1" in loader.conf to make it work. But that's not a SAS2008 or mps driver problem, that's a generic FreeBSD problem which also affects ixgbe, em and igb in my case. For some devices I use the trick to reload the kld (http://lists.freebsd.org/pipermail/freebsd-stable/2012-October/070200.ht= ml) Others also report that problem and also report that the problem doesn't occur on other guest OSs: http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/241447.html= So FreeBSD is doing some MSI-X initialization different at booting than all other OSs. Unfortunately I haven't had time to further help finding the real problem. -Harry --------------enig13364FC05F68CABA07F4A624 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlEc4GwACgkQLDqVQ9VXb8hMYACgmmpO2E6U2ccvMDqSM92XzAEa D2oAninnMiKe9UtXRv4XmlAAeikOkzio =RLp0 -----END PGP SIGNATURE----- --------------enig13364FC05F68CABA07F4A624--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?511CE06C.2080909>