<?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 R610 2.4GHz Unstable in Unleashed</title>
    <link>https://community.ruckuswireless.com/t5/Unleashed/R610-2-4GHz-Unstable/m-p/109309#M7059</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Setup a Ruckus R610 with Unleashed initially I had the latest firmware version and my 2.4GHz band was constantly resetting and bringing down all my SSIDs, I went back to an older version (200.14.6.1.203) and it seemed OK until I restarted the AP and now the 2.4GHz is very unstable again, with this showing in the logs:&lt;/P&gt;&lt;P&gt;Sep 8 07:05:03 Ruckus-R610 ZD-APMgr: IPC_thread rcv ping from TACMON&lt;BR /&gt;Sep 8 07:05:01 Ruckus-R610 kernel: [48302.769785] FWLOG: [49392031] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:05:01 Ruckus-R610 kernel: [48302.769768] FWLOG: [49392012] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:05:00 Ruckus-R610 kernel: [48301.768323] FWLOG: [49390879] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:05:00 Ruckus-R610 kernel: [48301.768307] FWLOG: [49390860] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:59 Ruckus-R610 kernel: [48300.766904] FWLOG: [49389727] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:59 Ruckus-R610 kernel: [48300.766886] FWLOG: [49389708] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:57 Ruckus-R610 kernel: [48298.763915] FWLOG: [49388575] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:57 Ruckus-R610 kernel: [48298.763897] FWLOG: [49388557] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:56 Ruckus-R610 kernel: [48297.762420] FWLOG: [49387423] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:56 Ruckus-R610 kernel: [48297.762403] FWLOG: [49387405] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:55 Ruckus-R610 kernel: [48296.760692] FWLOG: [49386271] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:55 Ruckus-R610 kernel: [48296.760674] FWLOG: [49386253] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:54 Ruckus-R610 kernel: [48295.759287] FWLOG: [49385119] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:54 Ruckus-R610 kernel: [48295.759270] FWLOG: [49385101] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:53 Ruckus-R610 kernel: [48294.757501] FWLOG: [49383968] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:53 Ruckus-R610 kernel: [48294.757483] FWLOG: [49383950] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:52 Ruckus-R610 kernel: [48293.756040] FWLOG: [49382816] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:52 Ruckus-R610 kernel: [48293.756023] FWLOG: [49382798] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:51 Ruckus-R610 kernel: [48292.754416] FWLOG: [49381664] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:51 Ruckus-R610 kernel: [48292.754399] FWLOG: [49381646] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:50 Ruckus-R610 kernel: [48291.752939] FWLOG: [49380513] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:50 Ruckus-R610 kernel: [48291.752920] FWLOG: [49380494] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 kernel: [48289.749728] FWLOG: [49379361] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 kernel: [48289.749711] FWLOG: [49379342] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): upgrade ap list all done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): update the version field of upgrade ap list node done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): target_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): backup_ver = 200.15.6.212.27!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): active_ver = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): upgrade_state = !&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): version_match = 0!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): imghdr.product = !&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): imghdr.version = !&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): firmware_file open failure&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): curr_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): target_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): upgrade_model_name = r710!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): target_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): curr_version_str=[200.14.6.1.203]&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): merge the election ap list to upgrade ap list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the vap firmware cluster done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the firmware cluster that have no any ap node done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): special handle the M510 node from upgrade_ap_list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the ap node that do not approved in ap_list from upgrade_ap_list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the ap node of upgrade_ap_list that do not exist in upgrade_ap_list_from_election done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): ap_node_find = 1!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): merge all ap from election to upgrade ap list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): update ap 60:d0:2c:0a:66:e0 attributes from election to upgrade ap list!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): add all models from election to upgrade ap list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): update time stamp to each ap node done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): now = 1757311488!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): is_system_upgrading = 0!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, get_ap_list(): see [/tmp/unleashed_upgrade/upgrade_ap_list_from_election.xml.ready], ap-list ready!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, get_ap_list(): ap-list loop 0.&lt;BR /&gt;Sep 8 07:04:47 Ruckus-R610 kernel: [48288.748237] FWLOG: [49378209] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:47 Ruckus-R610 kernel: [48288.748221] FWLOG: [49378190] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746505] FWLOG: [49377112] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746494] FWLOG: [49377094] WAL TX timeout wifi0 sig=fa33 txq 4 4 1 3&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746481] FWLOG: [49376429] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746464] FWLOG: [49376410] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Sep 2025 06:10:43 GMT</pubDate>
    <dc:creator>fortymarlin</dc:creator>
    <dc:date>2025-09-08T06:10:43Z</dc:date>
    <item>
      <title>R610 2.4GHz Unstable</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/R610-2-4GHz-Unstable/m-p/109309#M7059</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Setup a Ruckus R610 with Unleashed initially I had the latest firmware version and my 2.4GHz band was constantly resetting and bringing down all my SSIDs, I went back to an older version (200.14.6.1.203) and it seemed OK until I restarted the AP and now the 2.4GHz is very unstable again, with this showing in the logs:&lt;/P&gt;&lt;P&gt;Sep 8 07:05:03 Ruckus-R610 ZD-APMgr: IPC_thread rcv ping from TACMON&lt;BR /&gt;Sep 8 07:05:01 Ruckus-R610 kernel: [48302.769785] FWLOG: [49392031] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:05:01 Ruckus-R610 kernel: [48302.769768] FWLOG: [49392012] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:05:00 Ruckus-R610 kernel: [48301.768323] FWLOG: [49390879] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:05:00 Ruckus-R610 kernel: [48301.768307] FWLOG: [49390860] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:59 Ruckus-R610 kernel: [48300.766904] FWLOG: [49389727] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:59 Ruckus-R610 kernel: [48300.766886] FWLOG: [49389708] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:57 Ruckus-R610 kernel: [48298.763915] FWLOG: [49388575] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:57 Ruckus-R610 kernel: [48298.763897] FWLOG: [49388557] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:56 Ruckus-R610 kernel: [48297.762420] FWLOG: [49387423] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:56 Ruckus-R610 kernel: [48297.762403] FWLOG: [49387405] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:55 Ruckus-R610 kernel: [48296.760692] FWLOG: [49386271] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:55 Ruckus-R610 kernel: [48296.760674] FWLOG: [49386253] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:54 Ruckus-R610 kernel: [48295.759287] FWLOG: [49385119] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:54 Ruckus-R610 kernel: [48295.759270] FWLOG: [49385101] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:53 Ruckus-R610 kernel: [48294.757501] FWLOG: [49383968] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:53 Ruckus-R610 kernel: [48294.757483] FWLOG: [49383950] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:52 Ruckus-R610 kernel: [48293.756040] FWLOG: [49382816] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:52 Ruckus-R610 kernel: [48293.756023] FWLOG: [49382798] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:51 Ruckus-R610 kernel: [48292.754416] FWLOG: [49381664] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:51 Ruckus-R610 kernel: [48292.754399] FWLOG: [49381646] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:50 Ruckus-R610 kernel: [48291.752939] FWLOG: [49380513] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:50 Ruckus-R610 kernel: [48291.752920] FWLOG: [49380494] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 kernel: [48289.749728] FWLOG: [49379361] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 kernel: [48289.749711] FWLOG: [49379342] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): upgrade ap list all done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): update the version field of upgrade ap list node done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): target_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): backup_ver = 200.15.6.212.27!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): active_ver = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): upgrade_state = !&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): version_match = 0!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): imghdr.product = !&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): imghdr.version = !&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): firmware_file open failure&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): curr_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): target_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): upgrade_model_name = r710!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): target_version_str = 200.14.6.1.203!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): curr_version_str=[200.14.6.1.203]&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): merge the election ap list to upgrade ap list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the vap firmware cluster done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the firmware cluster that have no any ap node done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): special handle the M510 node from upgrade_ap_list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the ap node that do not approved in ap_list from upgrade_ap_list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): remove the ap node of upgrade_ap_list that do not exist in upgrade_ap_list_from_election done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): ap_node_find = 1!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): merge all ap from election to upgrade ap list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): update ap 60:d0:2c:0a:66:e0 attributes from election to upgrade ap list!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): add all models from election to upgrade ap list done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): update time stamp to each ap node done!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): now = 1757311488!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, insert_field_to_upgrade_ap_list(): is_system_upgrading = 0!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, get_ap_list(): see [/tmp/unleashed_upgrade/upgrade_ap_list_from_election.xml.ready], ap-list ready!&lt;BR /&gt;Sep 8 07:04:48 Ruckus-R610 syslog: upgrade_debug: pid=16514, get_ap_list(): ap-list loop 0.&lt;BR /&gt;Sep 8 07:04:47 Ruckus-R610 kernel: [48288.748237] FWLOG: [49378209] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:47 Ruckus-R610 kernel: [48288.748221] FWLOG: [49378190] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746505] FWLOG: [49377112] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746494] FWLOG: [49377094] WAL TX timeout wifi0 sig=fa33 txq 4 4 1 3&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746481] FWLOG: [49376429] WAL DEV reset, wifi0 rx 1, tx 1, reset =1 reason 2&lt;BR /&gt;Sep 8 07:04:46 Ruckus-R610 kernel: [48287.746464] FWLOG: [49376410] WAL TX timeout wifi0 sig=fa33 txq 0 7 1 3&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Sep 2025 06:10:43 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/R610-2-4GHz-Unstable/m-p/109309#M7059</guid>
      <dc:creator>fortymarlin</dc:creator>
      <dc:date>2025-09-08T06:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: R610 2.4GHz Unstable</title>
      <link>https://community.ruckuswireless.com/t5/Unleashed/R610-2-4GHz-Unstable/m-p/109337#M7064</link>
      <description>&lt;P&gt;Hi fortymarlin,&lt;/P&gt;&lt;P&gt;Thank you for posting your query!&lt;/P&gt;&lt;P&gt;I understand that you're experiencing instability with the R610 2.4GHz band.&lt;/P&gt;&lt;P&gt;Please try the following troubleshooting steps and let me know if they help:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Temporarily disable the 5GHz band to see if the instability persists on the 2.4GHz band alone.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create an open SSID and check if the issue occurs on that network.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For testing purpose If the issue continues, please take a backup of your configuration, then perform a factory reset on the access point. After that, re-flash the firmware and reapply your configuration.&lt;/P&gt;&lt;P&gt;If the problem is still not resolved, please log a ticket using the link below, and we will assist you further:&lt;/P&gt;&lt;P&gt;&lt;A href="https://support.ruckuswireless.com/contact-us" target="_blank" rel="noopener"&gt;https://support.ruckuswireless.com/contact-us&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I hope this information is helpful. If you have any concerns, please feel free to reach out.&lt;/P&gt;&lt;P&gt;Note: If this solution addresses your query, please consider marking this post as "Accepted Solution."&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;&lt;P&gt;Mayank&lt;/P&gt;</description>
      <pubDate>Mon, 08 Sep 2025 14:56:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Unleashed/R610-2-4GHz-Unstable/m-p/109337#M7064</guid>
      <dc:creator>Mayank</dc:creator>
      <dc:date>2025-09-08T14:56:20Z</dc:date>
    </item>
  </channel>
</rss>

