Hello,
On a HP Proliant ML350 G6 server with two LSI Logic / Symbios Logic LSI2008 SAS HBA's, I've got ESXi 5.0.0 (623860) installed.
~ # vmkload_mod -s mpt2sas |grep Version
Version: Version 06.00.00.00.6vmw, Build: 623860, Interface: 9.2 Built on: Feb 17 2012
This server made a purple screen last week with these error messages :
> 2013-07-04T16:32:38.106Z cpu0:2072)ALERT: LinScsi: SCSILinuxCmdDone:2220:Attempted double completion
> 2013-07-04T16:32:38.211Z cpu0:2072)@BlueScreen: Failed at vmkdrivers/src_9/vmklinux_9/vmware/linux_scsi.c:2221 — NOT REACHED
The problem is already known : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2013655
I have to apply patch Patch ESXi500-201303401-BG, which includes esx-base and a lot of drivers.
=> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2044374 for the patch information
=> http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2044373 for the build information
So I followed the KB and downloaded ESXi500-201303001.zip.
Digging into this patch, I found that the mpt2sas driver still has the same version as above (vib20/scsi-mpt2sas/VMware_bootbank_scsi-mpt2sas_06.00.00.00-6vmw.500.1.11.623860.vib) !
In fact, none of the drivers seem to have been updated, only esx-base does.
Looking a bit further, I found the latest release (Release date : 2013-04-02) of mpt2sas : https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESX5X-LSI-MPT2SAS-160000001VMW&productId=323 which can also be found on lsi.com (Driver-CD-ESX5_P16.zip). The file is mpt2sas-16.00.00.00.1vmw-1076887.zip
Does this version includes the correction to the purple screen error above (the release notes don't tell anything about this) ?
Considering the release date of version 16.0, could it be possible that VMWare made a mistake with ESXi500-201303001.zip patch and should have included this version 16.0 driver ? BTW, I notice that the download size for ESXi500-201303001.zip (311 Mb) on KB 2044373 is incorrect, it's in fact around 600 Mb.
Thanks in advance,
Loïc Mahé
RSI, Toulouse, France