<?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 MSM765 ath_txq_stuck_checker System Log Critical Errors in M and MSM Series</title>
    <link>https://community.hpe.com/t5/m-and-msm-series/msm765-ath-txq-stuck-checker-system-log-critical-errors/m-p/7034089#M6120</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Any one else seeing these errors?&amp;nbsp; I started seeing these a few days ago after noticing a large increase in snmp traffic.&amp;nbsp; Here is a sample:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Feb 8 10:14:38.799 crit MacAddress of AP kernel: ath_txq_stuck_checker ******** Software Q-3 is stuck txq:428663 txq_buf:1 mcast:31 !!!!&lt;BR /&gt;Feb 8 10:00:00.799 crit MacAddress of AP kernel: ath_txq_stuck_checker ******** Software Q-1 is stuck txq:14420059 txq_buf:3 mcast:2 !!!!&lt;BR /&gt;Feb 8 09:59:58.799 crit MacAddress of AP kernel: ath_txq_stuck_checker ******** Software Q-1 is stuck txq:14420059 txq_buf:3 mcast:0 !!!!&lt;BR /&gt;Feb 8 09:57:49.398 crit MacAddress of AP kernel: resetting the queues reset with LOSS for radio:wifi1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;My system:&lt;BR /&gt;MSM765 dual controllers firmware 6.6.9.0&lt;BR /&gt;About 200 AP's, mostly MSM430 and MSM460&lt;/P&gt;&lt;P&gt;History: Upgraded to 6.6.9.0 from 6.6.8.2 and these errors started occurring about 10 days later. There were no other changes to config, etc.&lt;BR /&gt;Troubleshooting so far: Have not noticed any impact on users as yet. Have tried disabling SNMP, turning off QOS in the VSC's, and turning off LLDP without any effect. Have rebooted all APs, the controllers, and have removed each of the dual controllers to eliminate hardware without any effect -- the errors continue.&lt;/P&gt;&lt;P&gt;I do not know if the firmware upgrade had anything to do with it as the problems did not start until about 10 days later.&amp;nbsp; Errors are from seemingly random AP's in the network, but maybe 20-30% have the errors at any point in time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 08 Feb 2019 17:48:38 GMT</pubDate>
    <dc:creator>UCRico</dc:creator>
    <dc:date>2019-02-08T17:48:38Z</dc:date>
    <item>
      <title>MSM765 ath_txq_stuck_checker System Log Critical Errors</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm765-ath-txq-stuck-checker-system-log-critical-errors/m-p/7034089#M6120</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Any one else seeing these errors?&amp;nbsp; I started seeing these a few days ago after noticing a large increase in snmp traffic.&amp;nbsp; Here is a sample:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Feb 8 10:14:38.799 crit MacAddress of AP kernel: ath_txq_stuck_checker ******** Software Q-3 is stuck txq:428663 txq_buf:1 mcast:31 !!!!&lt;BR /&gt;Feb 8 10:00:00.799 crit MacAddress of AP kernel: ath_txq_stuck_checker ******** Software Q-1 is stuck txq:14420059 txq_buf:3 mcast:2 !!!!&lt;BR /&gt;Feb 8 09:59:58.799 crit MacAddress of AP kernel: ath_txq_stuck_checker ******** Software Q-1 is stuck txq:14420059 txq_buf:3 mcast:0 !!!!&lt;BR /&gt;Feb 8 09:57:49.398 crit MacAddress of AP kernel: resetting the queues reset with LOSS for radio:wifi1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;My system:&lt;BR /&gt;MSM765 dual controllers firmware 6.6.9.0&lt;BR /&gt;About 200 AP's, mostly MSM430 and MSM460&lt;/P&gt;&lt;P&gt;History: Upgraded to 6.6.9.0 from 6.6.8.2 and these errors started occurring about 10 days later. There were no other changes to config, etc.&lt;BR /&gt;Troubleshooting so far: Have not noticed any impact on users as yet. Have tried disabling SNMP, turning off QOS in the VSC's, and turning off LLDP without any effect. Have rebooted all APs, the controllers, and have removed each of the dual controllers to eliminate hardware without any effect -- the errors continue.&lt;/P&gt;&lt;P&gt;I do not know if the firmware upgrade had anything to do with it as the problems did not start until about 10 days later.&amp;nbsp; Errors are from seemingly random AP's in the network, but maybe 20-30% have the errors at any point in time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Feb 2019 17:48:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm765-ath-txq-stuck-checker-system-log-critical-errors/m-p/7034089#M6120</guid>
      <dc:creator>UCRico</dc:creator>
      <dc:date>2019-02-08T17:48:38Z</dc:date>
    </item>
    <item>
      <title>Re: MSM765 ath_txq_stuck_checker System Log Critical Errors</title>
      <link>https://community.hpe.com/t5/m-and-msm-series/msm765-ath-txq-stuck-checker-system-log-critical-errors/m-p/7035080#M6124</link>
      <description>&lt;P&gt;&lt;FONT size="3"&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;&lt;SPAN&gt;As per internal update, these are nomral&amp;nbsp; recovery mechanism messages. This version (6.6.9.0) is introduced wth&amp;nbsp;new recovery mechanisms&amp;nbsp;to mitigate "stuck queue" issues and is&amp;nbsp;related to soft reset of the radio.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="3"&gt;If you start seeing these messages more frequently and impacting the network, you may log a support case for deeper investigation.&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 18 Feb 2019 06:20:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/m-and-msm-series/msm765-ath-txq-stuck-checker-system-log-critical-errors/m-p/7035080#M6124</guid>
      <dc:creator>drk787</dc:creator>
      <dc:date>2019-02-18T06:20:06Z</dc:date>
    </item>
  </channel>
</rss>

