<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Log spew in VMware vCenter™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401364#M19632</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"&lt;SPAN class="head_h5"&gt;HPE has released SPP 2017.07.2 as a replacement for SPP 2017.07.1 due to a recently discovered Software/Firmware issue with the HPE QLogic NX2 10/20GbE Multifunction Drivers for VMware vSphere 6.0/6.5, version 2017.07.07 "&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="head_h5"&gt;Source: &lt;A href="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx" title="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx"&gt;Service Pack for ProLiant | Hewlett Packard Enterprise&lt;/A&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Sep 2017 23:55:04 GMT</pubDate>
    <dc:creator>Bleeder</dc:creator>
    <dc:date>2017-09-26T23:55:04Z</dc:date>
    <item>
      <title>Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401357#M19625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have updated driver &amp;amp; firmware for the Broadcom 10Gb NICS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since then we have seen the following log spew on the host:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2016-01-14T10:11:25.323Z cpu12:33130)&amp;lt;3&amp;gt;[bnx2x_alloc_rx_sge:734(vmnic0)]Can't alloc sge&lt;/P&gt;&lt;P&gt;2016-01-14T10:11:26.186Z cpu12:33130)&amp;lt;3&amp;gt;[bnx2x_alloc_rx_sge:734(vmnic0)]Can't alloc sge&lt;/P&gt;&lt;P&gt;2016-01-14T10:11:27.189Z cpu12:33130)&amp;lt;3&amp;gt;[bnx2x_alloc_rx_sge:734(vmnic0)]Can't alloc sge&lt;/P&gt;&lt;P&gt;2016-01-14T10:11:27.989Z cpu12:33599)&amp;lt;3&amp;gt;[bnx2x_alloc_rx_sge:734(vmnic0)]Can't alloc sge&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone experience similar or know if this is a concern?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Feb 2016 10:11:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401357#M19625</guid>
      <dc:creator>New_User_999</dc:creator>
      <dc:date>2016-02-09T10:11:55Z</dc:date>
    </item>
    <item>
      <title>Re: Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401358#M19626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This has been fixed with new driver: &lt;/P&gt;&lt;P&gt;&lt;A href="https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI55-QLOGIC-NIC-BNX2X-271310V554&amp;amp;productId=353" title="https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXI55-QLOGIC-NIC-BNX2X-271310V554&amp;amp;productId=353"&gt;VMware vSphere 5: Private Cloud Computing, Server and Data Center Virtualization&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 May 2016 15:56:36 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401358#M19626</guid>
      <dc:creator>mavatko</dc:creator>
      <dc:date>2016-05-04T15:56:36Z</dc:date>
    </item>
    <item>
      <title>Re: Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401359#M19627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we have experienced weird problems with upload (stalled) on some heavy network utilized vms. ESXi hosts were HPs blades with driver 2.712.70.v55.3 (fw 7.13.23), what is recommended version in HP recipe (&lt;A href="https://vibsdepot.hpe.com/hpq/recipes/HPE-VMware-Recipe.pdf" title="https://vibsdepot.hpe.com/hpq/recipes/HPE-VMware-Recipe.pdf"&gt;https://vibsdepot.hpe.com/hpq/recipes/HPE-VMware-Recipe.pdf&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;esxi logs with version 2.712.70.v55.3 are full of&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2016-06-27T16:28:23.868Z cpu14:32868)&amp;lt;3&amp;gt;[bnx2x_esx_init_rx_ring:1946(vmnic0)]disabling TPA for queue[1]&lt;/P&gt;&lt;P&gt;2016-06-27T16:28:23.890Z cpu14:32868)&amp;lt;3&amp;gt;[bnx2x_dynamic_alloc_rx_queue_single:789(vmnic0)]Could not start queue:1&lt;/P&gt;&lt;P&gt;2016-06-27T16:28:28.866Z cpu0:32868)&amp;lt;3&amp;gt;[bnx2x_alloc_rx_sge:734(vmnic0)]Can't alloc sge&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are testing this never version 2.713.10.v55.4 and it seems promising. I'm planing opening support case with vmware and hp.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have found&amp;nbsp; &lt;A href="https://communities.vmware.com/thread/535624"&gt;Slow backup performance&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mentioning this errors related to slow performance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Jun 2016 13:47:32 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401359#M19627</guid>
      <dc:creator>ivanerben</dc:creator>
      <dc:date>2016-06-28T13:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401360#M19628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Have a look at this.&lt;/P&gt;&lt;P&gt;This is a driver issue.&lt;/P&gt;&lt;P&gt;&lt;A href="http://vmfszone.blogspot.com.tr/2016/08/cant-alloc-sge.html" title="http://vmfszone.blogspot.com.tr/2016/08/cant-alloc-sge.html"&gt;VMWARE: Can't alloc sge&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Aug 2016 07:29:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401360#M19628</guid>
      <dc:creator>scelikag</dc:creator>
      <dc:date>2016-08-31T07:29:33Z</dc:date>
    </item>
    <item>
      <title>Re: Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401361#M19629</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;after year we are experiencing similar behavior after updates. ESXi is 6.5 Update 1 (6.5.0 #1 SMP Release build-5969303 Jul&amp;nbsp; 6 2017) with latest HP driver&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; Driver Info:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Bus Info: 0000:04:00.1&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Driver: bnx2x&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Firmware Version: bc 7.13.75&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Version: 2.713.30.v60.7&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have found that newer driver should exist, but download is not available at &lt;A href="https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX60-QLOGIC-BNX2X-271330V608-1OEM&amp;amp;productId=491#product_downloads" title="https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESX60-QLOGIC-BNX2X-271330V608-1OEM&amp;amp;productId=491#product_downloads"&gt;Download VMware vSphere&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also have found blog post which mentions some bricked network adapters with this driver &lt;A href="http://www.thevirtualist.org/bricked-qlogic-broadcom-bcm57840-driver-update/" title="http://www.thevirtualist.org/bricked-qlogic-broadcom-bcm57840-driver-update/"&gt;http://www.thevirtualist.org/bricked-qlogic-broadcom-bcm57840-driver-update/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.thevirtualist.org/bricked-qlogic-broadcom-bcm57840-driver-update/" title="http://www.thevirtualist.org/bricked-qlogic-broadcom-bcm57840-driver-update/"&gt;http://www.thevirtualist.org/bricked-qlogic-broadcom-bcm57840-driver-update/&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe that is reason for call out?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone experiencing same bahavior again?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Sep 2017 15:12:47 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401361#M19629</guid>
      <dc:creator>ivanerben</dc:creator>
      <dc:date>2017-09-07T15:12:47Z</dc:date>
    </item>
    <item>
      <title>Re: Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401362#M19630</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please see this link for the newer driver - &lt;A href="https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESX60-QLOGIC-BNX2X-271330V608&amp;amp;productId=491&amp;amp;download=true&amp;amp;fileId=1f8c6c51314b103450c0fcef0ec89903&amp;amp;secureParam=cf3851b01476c4c250de8be1ae9fa2cf&amp;amp;uuId=f730a0a8-193a-4650-bd8d-280abff2d765&amp;amp;downloadType=" title="https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESX60-QLOGIC-BNX2X-271330V608&amp;amp;productId=491&amp;amp;download=true&amp;amp;fileId=1f8c6c51314b103450c0fcef0ec89903&amp;amp;secureParam=cf3851b01476c4c250de8be1ae9fa2cf&amp;amp;uuId=f730a0a8-193a-4650-bd8d-280abff2d765&amp;amp;downloadType="&gt;https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESX60-QLOGIC-BNX2X-271330V608&amp;amp;productId=491&amp;amp;download=true&amp;amp;fi…&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the same issue on Broadcom cards in my hosts with this in the logs and it is actually causing APD in my iSCSI adapters.&amp;nbsp; I am going to try the newer driver to see what happens as we have the latest firmware - 7.14.37.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Sep 2017 17:15:55 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401362#M19630</guid>
      <dc:creator>cchilderhose528</dc:creator>
      <dc:date>2017-09-11T17:15:55Z</dc:date>
    </item>
    <item>
      <title>Re: Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401363#M19631</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you for link for the driver, finally I have release notes. I have found driver itself before in dell iso image and extracted it, but without change log.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can see there&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;2. Problem: CQ93244: VM traffic stops after error recovery.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Change:Invoke stop_queue() before disable TPA, to aviod memory leak.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Free Rx filter table during Recovery unload, to avoid memory leak.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Introduced: 2.713.30.v[50,55,60].1&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;We can see in logs that memleak before first bnx2x_esx_init_rx_ring error:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;2017-09-19T21:18:34.615Z cpu3:65645)vmklinux: alloc_pages:1010: This message has repeated 1 times: gfp_mask=0xd0, order=0x0, vmk_PktSlabAllocPage returned 'Out of memory'&lt;/P&gt;&lt;P&gt;2017-09-19T21:18:34.615Z cpu3:65645)&amp;lt;3&amp;gt;[bnx2x_esx_init_rx_ring:1960(vmnic0)]was only able to allocate 192 rx sges&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;It seems HPE image iso and HPE drivers relase contains this problematic driver. DELL have newer - fixed driver.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Sep 2017 09:07:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401363#M19631</guid>
      <dc:creator>ivanerben</dc:creator>
      <dc:date>2017-09-20T09:07:04Z</dc:date>
    </item>
    <item>
      <title>Re: Log spew</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401364#M19632</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"&lt;SPAN class="head_h5"&gt;HPE has released SPP 2017.07.2 as a replacement for SPP 2017.07.1 due to a recently discovered Software/Firmware issue with the HPE QLogic NX2 10/20GbE Multifunction Drivers for VMware vSphere 6.0/6.5, version 2017.07.07 "&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="head_h5"&gt;Source: &lt;A href="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx" title="http://h17007.www1.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx"&gt;Service Pack for ProLiant | Hewlett Packard Enterprise&lt;/A&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Sep 2017 23:55:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Log-spew/m-p/1401364#M19632</guid>
      <dc:creator>Bleeder</dc:creator>
      <dc:date>2017-09-26T23:55:04Z</dc:date>
    </item>
  </channel>
</rss>

