kongac - wl0: PSM microcode watchdog fired

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
View previous topic :: View next topic  
Author Message
mazecreator
DD-WRT Novice


Joined: 09 May 2009
Posts: 48
PostPosted: Sun May 19, 2019 16:53    Post subject: kongac - wl0: PSM microcode watchdog fired Reply with quote
I have been getting an error which appears to disable the WiFi for a short period of time. I decided to report it now as I have seen it for the last fer KONG builds. I haven't tested the May Version yet. I have seen this on two different models of routers and think it might be related to the 2.4 GHz load on the router. Also, I have only seen this on my units configured as AP and not the main router (Main router probably doesn't see a lot of 2.4 GHz device traffic).

The following errors occurred on the following unit:
Netgear R6400 v1
DD-WRT v3.0-r39575M kongac (04/20/19)

======================================
Code:
08:52:05.380  192.168.0.4  kern.warn      May 19 08:52:04 kernel: ucode revision 928.10006
08:52:05.380  192.168.0.4  kern.warn      May 19 08:52:04 kernel: wl0: PSM microcode watchdog fired at 117670 (seconds)
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel: wl0: psmdebug 0x00ff9159, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off
08:53:57.615  192.168.0.4  daemon.debug   May 19 08:53:57 ntpclient[10336]: Connecting to pool.ntp.org [216.229.0.50] ...
08:53:57.678  192.168.0.4  daemon.info    May 19 08:53:57 ntpclient[10336]: Time set from pool.ntp.org [216.229.0.50].
08:53:57.679  192.168.0.4  daemon.info    May 19 08:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
09:53:57.834  192.168.0.4  daemon.debug   May 19 09:53:57 ntpclient[10610]: Connecting to pool.ntp.org [199.102.46.79] ...
09:53:57.874  192.168.0.4  daemon.info    May 19 09:53:57 ntpclient[10610]: Time set from pool.ntp.org [199.102.46.79].
09:53:57.875  192.168.0.4  daemon.info    May 19 09:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
10:53:58.027  192.168.0.4  daemon.debug   May 19 10:53:57 ntpclient[10884]: Connecting to pool.ntp.org [66.220.10.2] ...
10:53:58.112  192.168.0.4  daemon.info    May 19 10:53:57 ntpclient[10884]: Time set from pool.ntp.org [66.220.10.2].
10:53:58.113  192.168.0.4  daemon.info    May 19 10:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: ucode revision 928.10006
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: wl0: PSM microcode watchdog fired at 127090 (seconds)
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: wl0: psmdebug 0x00ff92a2, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off
11:53:58.253  192.168.0.4  daemon.debug   May 19 11:53:57 ntpclient[11158]: Connecting to pool.ntp.org [204.2.134.162] ...
11:53:58.345  192.168.0.4  daemon.info    May 19 11:53:57 ntpclient[11158]: Time set from pool.ntp.org [204.2.134.162].
11:53:58.345  192.168.0.4  daemon.info    May 19 11:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: ucode revision 928.10006
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) phydebug PC ampdu clk off
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: wl0: PSM microcode watchdog fired at 129020 (seconds)
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: wl0: psmdebug 0x00ff8c4c, phydebug 0x00000031, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x80b2 m_cts_duration 0x0000 m_ucode_dbgst 0x0002
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000


I have also seen this error reported on a unit configured as AP as well:
Buffalo WZR-1750DHP
DD-WRT v3.0-r39575M kongac (04/20/19)

I have nothing recent from errors on the 1750 as I think it is based upon where the wifi devices attach. I do recall that the error is reported against "wl1" rather than 0 as the order of the devices is flipped on the 1750 vs the 6400.

Any idea what might be the issue here? It does disconnect the wifi which causes faults with some of the clients. The clients usually are cameras that don't support the 5.0 GHz frequency so I can't just move them to the 5.0 SSID.


EDIT: Just got this reported on the 1750:

Code:
13:34:34.177  192.168.0.10  kern.warn      May 19 13:34:33 kernel: ucode revision 928.10006
13:34:34.177  192.168.0.10  kern.warn      May 19 13:34:33 kernel: wl1: PSM microcode watchdog fired at 99682 (seconds)
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel: wl1: psmdebug 0x00ff8c4c, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160403 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off
Back to top View user's profile Send private message
Sponsor
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany
PostPosted: Sun May 19, 2019 18:31    Post subject: Re: kongac - wl0: PSM microcode watchdog fired Reply with quote
mazecreator wrote:
I have been getting an error which appears to disable the WiFi for a short period of time. I decided to report it now as I have seen it for the last fer KONG builds. I haven't tested the May Version yet. I have seen this on two different models of routers and think it might be related to the 2.4 GHz load on the router. Also, I have only seen this on my units configured as AP and not the main router (Main router probably doesn't see a lot of 2.4 GHz device traffic).

The following errors occurred on the following unit:
Netgear R6400 v1
DD-WRT v3.0-r39575M kongac (04/20/19)

======================================
Code:
08:52:05.380  192.168.0.4  kern.warn      May 19 08:52:04 kernel: ucode revision 928.10006
08:52:05.380  192.168.0.4  kern.warn      May 19 08:52:04 kernel: wl0: PSM microcode watchdog fired at 117670 (seconds)
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel: wl0: psmdebug 0x00ff9159, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off
08:53:57.615  192.168.0.4  daemon.debug   May 19 08:53:57 ntpclient[10336]: Connecting to pool.ntp.org [216.229.0.50] ...
08:53:57.678  192.168.0.4  daemon.info    May 19 08:53:57 ntpclient[10336]: Time set from pool.ntp.org [216.229.0.50].
08:53:57.679  192.168.0.4  daemon.info    May 19 08:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
09:53:57.834  192.168.0.4  daemon.debug   May 19 09:53:57 ntpclient[10610]: Connecting to pool.ntp.org [199.102.46.79] ...
09:53:57.874  192.168.0.4  daemon.info    May 19 09:53:57 ntpclient[10610]: Time set from pool.ntp.org [199.102.46.79].
09:53:57.875  192.168.0.4  daemon.info    May 19 09:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
10:53:58.027  192.168.0.4  daemon.debug   May 19 10:53:57 ntpclient[10884]: Connecting to pool.ntp.org [66.220.10.2] ...
10:53:58.112  192.168.0.4  daemon.info    May 19 10:53:57 ntpclient[10884]: Time set from pool.ntp.org [66.220.10.2].
10:53:58.113  192.168.0.4  daemon.info    May 19 10:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: ucode revision 928.10006
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: wl0: PSM microcode watchdog fired at 127090 (seconds)
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: wl0: psmdebug 0x00ff92a2, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off
11:53:58.253  192.168.0.4  daemon.debug   May 19 11:53:57 ntpclient[11158]: Connecting to pool.ntp.org [204.2.134.162] ...
11:53:58.345  192.168.0.4  daemon.info    May 19 11:53:57 ntpclient[11158]: Time set from pool.ntp.org [204.2.134.162].
11:53:58.345  192.168.0.4  daemon.info    May 19 11:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: ucode revision 928.10006
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) phydebug PC ampdu clk off
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: wl0: PSM microcode watchdog fired at 129020 (seconds)
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: wl0: psmdebug 0x00ff8c4c, phydebug 0x00000031, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x80b2 m_cts_duration 0x0000 m_ucode_dbgst 0x0002
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000


I have also seen this error reported on a unit configured as AP as well:
Buffalo WZR-1750DHP
DD-WRT v3.0-r39575M kongac (04/20/19)

I have nothing recent from errors on the 1750 as I think it is based upon where the wifi devices attach. I do recall that the error is reported against "wl1" rather than 0 as the order of the devices is flipped on the 1750 vs the 6400.

Any idea what might be the issue here? It does disconnect the wifi which causes faults with some of the clients. The clients usually are cameras that don't support the 5.0 GHz frequency so I can't just move them to the 5.0 SSID.


EDIT: Just got this reported on the 1750:

Code:
13:34:34.177  192.168.0.10  kern.warn      May 19 13:34:33 kernel: ucode revision 928.10006
13:34:34.177  192.168.0.10  kern.warn      May 19 13:34:33 kernel: wl1: PSM microcode watchdog fired at 99682 (seconds)
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel: wl1: psmdebug 0x00ff8c4c, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160403 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off



One or more of your wireless clients are the problem, they do not respond correctly and after some time the radio will reset in order to clear out session data. This causes short wireless downtime. You could turn off powermanagement stuff, but then you completely limit your wireless to g rates.
_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Back to top View user's profile Send private message
mazecreator
DD-WRT Novice


Joined: 09 May 2009
Posts: 48
PostPosted: Sun May 19, 2019 18:44    Post subject: Re: kongac - wl0: PSM microcode watchdog fired Reply with quote
<Kong> wrote:
mazecreator wrote:
I have been getting an error which appears to disable the WiFi for a short period of time. I decided to report it now as I have seen it for the last fer KONG builds. I haven't tested the May Version yet. I have seen this on two different models of routers and think it might be related to the 2.4 GHz load on the router. Also, I have only seen this on my units configured as AP and not the main router (Main router probably doesn't see a lot of 2.4 GHz device traffic).

The following errors occurred on the following unit:
Netgear R6400 v1
DD-WRT v3.0-r39575M kongac (04/20/19)

======================================
Code:
08:52:05.380  192.168.0.4  kern.warn      May 19 08:52:04 kernel: ucode revision 928.10006
08:52:05.380  192.168.0.4  kern.warn      May 19 08:52:04 kernel: wl0: PSM microcode watchdog fired at 117670 (seconds)
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel: wl0: psmdebug 0x00ff9159, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
08:52:05.381  192.168.0.4  kern.warn      May 19 08:52:04 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off
08:53:57.615  192.168.0.4  daemon.debug   May 19 08:53:57 ntpclient[10336]: Connecting to pool.ntp.org [216.229.0.50] ...
08:53:57.678  192.168.0.4  daemon.info    May 19 08:53:57 ntpclient[10336]: Time set from pool.ntp.org [216.229.0.50].
08:53:57.679  192.168.0.4  daemon.info    May 19 08:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
09:53:57.834  192.168.0.4  daemon.debug   May 19 09:53:57 ntpclient[10610]: Connecting to pool.ntp.org [199.102.46.79] ...
09:53:57.874  192.168.0.4  daemon.info    May 19 09:53:57 ntpclient[10610]: Time set from pool.ntp.org [199.102.46.79].
09:53:57.875  192.168.0.4  daemon.info    May 19 09:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
10:53:58.027  192.168.0.4  daemon.debug   May 19 10:53:57 ntpclient[10884]: Connecting to pool.ntp.org [66.220.10.2] ...
10:53:58.112  192.168.0.4  daemon.info    May 19 10:53:57 ntpclient[10884]: Time set from pool.ntp.org [66.220.10.2].
10:53:58.113  192.168.0.4  daemon.info    May 19 10:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: ucode revision 928.10006
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: wl0: PSM microcode watchdog fired at 127090 (seconds)
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: wl0: psmdebug 0x00ff92a2, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
11:30:30.411  192.168.0.4  kern.warn      May 19 11:30:29 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off
11:53:58.253  192.168.0.4  daemon.debug   May 19 11:53:57 ntpclient[11158]: Connecting to pool.ntp.org [204.2.134.162] ...
11:53:58.345  192.168.0.4  daemon.info    May 19 11:53:57 ntpclient[11158]: Time set from pool.ntp.org [204.2.134.162].
11:53:58.345  192.168.0.4  daemon.info    May 19 11:53:57 process_monitor[1287]: cyclic NTP Update success (servers pool.ntp.org)
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: ucode revision 928.10006
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) phydebug PC ampdu clk off
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: wl0: PSM microcode watchdog fired at 129020 (seconds)
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel: wl0: psmdebug 0x00ff8c4c, phydebug 0x00000031, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160402 ifsstat 0x80b2 m_cts_duration 0x0000 m_ucode_dbgst 0x0002
12:02:57.832  192.168.0.4  kern.warn      May 19 12:02:57 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000


I have also seen this error reported on a unit configured as AP as well:
Buffalo WZR-1750DHP
DD-WRT v3.0-r39575M kongac (04/20/19)

I have nothing recent from errors on the 1750 as I think it is based upon where the wifi devices attach. I do recall that the error is reported against "wl1" rather than 0 as the order of the devices is flipped on the 1750 vs the 6400.

Any idea what might be the issue here? It does disconnect the wifi which causes faults with some of the clients. The clients usually are cameras that don't support the 5.0 GHz frequency so I can't just move them to the 5.0 SSID.


EDIT: Just got this reported on the 1750:

Code:
13:34:34.177  192.168.0.10  kern.warn      May 19 13:34:33 kernel: ucode revision 928.10006
13:34:34.177  192.168.0.10  kern.warn      May 19 13:34:33 kernel: wl1: PSM microcode watchdog fired at 99682 (seconds)
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel: wl1: psmdebug 0x00ff8c4c, phydebug 0x00000000, psm_brc 0x0100 psm_brc_1 0x0058maccontrol 0x84160403 ifsstat 0x00af m_cts_duration 0x0000 m_ucode_dbgst 0x0002
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel:      wepctl 0x8770, pcmctl 0x0309, pcmstat 0x0000
13:34:34.178  192.168.0.10  kern.warn      May 19 13:34:33 kernel: M_RXFRM_BLK scr(0:63) btc_params(0:63) PC ampdu clk off



One or more of your wireless clients are the problem, they do not respond correctly and after some time the radio will reset in order to clear out session data. This causes short wireless downtime. You could turn off powermanagement stuff, but then you completely limit your wireless to g rates.


Thanks Kong for the fast reply! Great work on the firmware too!

I don't mind loosing speed on the 2.4, but not sure how to turn off power management. I looked for settings but couldn't find them. Also, I don't see anything on the Foscam Camera clients either (I suspect these are the culprits causing the problem).

Can you point me to a FAQ or something to help me disable the power management?
Back to top View user's profile Send private message
gijswijs
DD-WRT Novice


Joined: 23 Oct 2020
Posts: 3
PostPosted: Tue Oct 27, 2020 2:37    Post subject: Did you fix it? Reply with quote
@mazecreator Did you find a fix for it? I think I might have a similar problem.

Currently the only way for me to have a working router is to disable wl1 entirely. I now have a very fancy router with no 5ghz connectivity. Crying or Very sad
Back to top View user's profile Send private message
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum