Problems with the LSI 9211-8i or LSI SAS2008 chips?

[Harald Schmalzbauer]

 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 pci3
> mps0: Firmware: 14.00.00.00, Driver: 14.00.00.01-fbsd
> mps0: IOCCapabilities:
> 1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
>
> 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 simply
> 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=1" 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.html)
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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20130214/48d29573/attachment.sig>