<?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 some weird error on show log buffer in ExtremeWireless (IQE)</title>
    <link>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89368#M1109</link>
    <description>&lt;P&gt;I occasionally `show log buffer` and saw some error:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl_add_timer: Already set. Name: wnm_bss_idle_timer, per 1&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: 4 rx hlfifo overflows!&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from cc:f9:e4:bb:37:f8 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from cc:b0:da:fe:c9:6f decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 84:ef:18:6e:9b:50 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 20:16:b9:65:c7:f0 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 9c:b6:d0:f7:0c:d5 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from cc:f9:e4:bb:37:f8 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 20:16:b9:65:c7:f0 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from e4:02:9b:41:96:9b decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 98:54:1b:d9:55:44 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 44:03:2c:7c:04:66 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 44:03:2c:7c:04:66 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:35 info    last message repeated 2 times&lt;BR /&gt;2021-07-23 11:20:35 info    ah_auth: aaa: pmksa_cache_auth_add: own_addr 9c5d:1249:2be4, sta 5c66:6c60:ca55, 1, username guoyingying&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xd42 for 200 ms&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: link up (wifi1.1)&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_watchdog HAMMERING due to too many phy tx error in 1s&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;and idea what is wrong?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 23 Jul 2021 11:06:19 GMT</pubDate>
    <dc:creator>zlinuxboy</dc:creator>
    <dc:date>2021-07-23T11:06:19Z</dc:date>
    <item>
      <title>some weird error on show log buffer</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89368#M1109</link>
      <description>&lt;P&gt;I occasionally `show log buffer` and saw some error:&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl_add_timer: Already set. Name: wnm_bss_idle_timer, per 1&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: 4 rx hlfifo overflows!&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from cc:f9:e4:bb:37:f8 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from cc:b0:da:fe:c9:6f decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 84:ef:18:6e:9b:50 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 20:16:b9:65:c7:f0 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 9c:b6:d0:f7:0c:d5 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from cc:f9:e4:bb:37:f8 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 20:16:b9:65:c7:f0 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from e4:02:9b:41:96:9b decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 98:54:1b:d9:55:44 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 44:03:2c:7c:04:66 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:38 info    kernel: [wifi]: wl1: wlc_recvdata_ordered: frame from 44:03:2c:7c:04:66 decrypt failed: -48&lt;BR /&gt;2021-07-23 11:20:35 info    last message repeated 2 times&lt;BR /&gt;2021-07-23 11:20:35 info    ah_auth: aaa: pmksa_cache_auth_add: own_addr 9c5d:1249:2be4, sta 5c66:6c60:ca55, 1, username guoyingying&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_ampdu_resp_timeout: cleaning up resp tid 0 waiting forseq 0xd42 for 200 ms&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: link up (wifi1.1)&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_watchdog HAMMERING due to too many phy tx error in 1s&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1 wlc_txbf_set_shm_idx: scb aleady has user index 255&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: wl1: wlc_txbf_init_exp failed to set shm idx&lt;BR /&gt;2021-07-23 11:20:35 info    kernel: [wifi]: 1 wlc_txbf_set_shm_idx: fail to find a free user index&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;and idea what is wrong?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jul 2021 11:06:19 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89368#M1109</guid>
      <dc:creator>zlinuxboy</dc:creator>
      <dc:date>2021-07-23T11:06:19Z</dc:date>
    </item>
    <item>
      <title>Re: some weird error on show log buffer</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89369#M1110</link>
      <description>&lt;P&gt;Looking at cases with similar errors, seems like it’s linked to radio frequency interference and high CPU, I’d recommend checking those first. Some cases also saw improvement after disabling MU-MIMO and QoS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That said, all the cases I can find with these errors are for much older firmware versions, are you seeing these messages while using the latest firmware available for your model?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Jul 2021 22:15:35 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89369#M1110</guid>
      <dc:creator>SamPirok</dc:creator>
      <dc:date>2021-07-23T22:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: some weird error on show log buffer</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89370#M1111</link>
      <description>&lt;P&gt;Yes, ap230 is running 10.3.3.&lt;/P&gt;</description>
      <pubDate>Sat, 24 Jul 2021 06:55:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89370#M1111</guid>
      <dc:creator>zlinuxboy</dc:creator>
      <dc:date>2021-07-24T06:55:54Z</dc:date>
    </item>
    <item>
      <title>Re: some weird error on show log buffer</title>
      <link>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89371#M1112</link>
      <description>&lt;P&gt;Thank you for letting me know. In that case, I would suggest checking the CPU on the AP to make sure it looks normal. &lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000056717&amp;amp;q=How%20to%20check%20CPU%20on%20IQE%20device" target="_blank" rel="noreferrer noopener"&gt;This guide reviews how to check and troubleshoot CPU on IQE devices.&amp;nbsp;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If that looks normal, I’d check the levels of radio frequency (RF) interference on the AP. &lt;A href="https://extremeportal.force.com/ExtrArticleDetail?an=000079422&amp;amp;q=radio%20frequency%20interference" target="_blank" rel="noreferrer noopener"&gt;This guide reviews how to identify RF interference and how to troubleshoot for the different causes of that.&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Other than that, if you have MU-MIMO enabled, try disabling it and monitoring the AP for a couple hours if possible to see if that clears up the logs. Also, if you’re using QoS in your user profiles, I’d suggest switching to a default QoS object and/or no QoS to see if that clears up those messages.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If none of that helps, I’d recommend opening a support case and letting them know what you’ve tried so far.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jul 2021 19:23:43 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremewireless-iqe/some-weird-error-on-show-log-buffer/m-p/89371#M1112</guid>
      <dc:creator>SamPirok</dc:creator>
      <dc:date>2021-07-26T19:23:43Z</dc:date>
    </item>
  </channel>
</rss>

