What's new

kernel: FPM Pool 1: invalid token 0x21950000 freed

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I have the same error on my AX88U's. Does this happen on stock firmware as well? If so, we should each submit a ticket to ASUS so they can look into it.

Yeah i am on stock firmware unless some one reflashed and returned it box was't even having a seal altho it did't really worry me maybe annoy me a bit.

My firmware
upload_2019-11-11_16-38-0.png


If flashed dd wrt in the past on my netgear, i did send ticket but they say to return it i dont think they have any idea that all there routers have error message.
 
Hi, I have nailed these errors down a bit. In my router these tend to appear when there is high speed wifi data transfer going through the router (either 5Ghz or 2.4Ghz). They do not appear when there is high speed data transfer to a cabled device or to the router itself from the WAN. Normally these can just be ignored, but some times they *do* interfere with router behavior and end up causing a reboot or wifi drops or inability to authenticate/establish a wifi connection requiring router reboot.
 
Hi, I have nailed these errors down a bit. In my router these tend to appear when there is high speed wifi data transfer going through the router (either 5Ghz or 2.4Ghz). They do not appear when there is high speed data transfer to a cabled device or to the router itself from the WAN. Normally these can just be ignored, but some times they *do* interfere with router behavior and end up causing a reboot or wifi drops or inability to authenticate/establish a wifi connection requiring router reboot.

I was trying to force that error while pulling files from the nas on my laptop with 60 MB/s thats the highest i can get from my laptop right now with my 7260 intel wifi but no errors, while spaming speedtest.net with test after test did't do anything either, only seems to happen with my huawei p10 lite so far, it either happens a lot or does't happen for a long time.
 
Hi, I have nailed these errors down a bit. In my router these tend to appear when there is high speed wifi data transfer going through the router (either 5Ghz or 2.4Ghz). They do not appear when there is high speed data transfer to a cabled device or to the router itself from the WAN. Normally these can just be ignored, but some times they *do* interfere with router behavior and end up causing a reboot or wifi drops or inability to authenticate/establish a wifi connection requiring router reboot.
I'll check it this evening with my Intel ax200ngw card if I can trigger this error with a download. I get easily 1.2Gb/sec with that one.
 
I have the same error on my AX88U's. Does this happen on stock firmware as well? If so, we should each submit a ticket to ASUS so they can look into it.

The RT-AX88U is going to get an SDK upgrade with the next firmware release (adding WPA3 and OFDMA support), so at this point it's pointless to submit tickets about this. Chances also are that any ticket would be ignored, since end users aren't reporting an actual functionality issue. For all we know, this may very well simply be debugging output intended for developers, and not the sign of an actual problem.

FPM is Broadcom's pool-based memory manager.
 
Asus just responded to my ticket saying its isolated incident probably faulty device, even tho there latest flagship ax11000 also gets same error simple google search you find many users with that error if its a debug message or not only asus can find out i guess if they go talk with broadcom and asks them what that message means.
 
Hi, anyone seeing this error with 7756 based firmwre ? (either the official one or Merlin 'new specially compliled' 384.14 beta3 that incorporates it). Just curious. I will most likely start testing it this afternoon ... I will post my findings here.
 
With the new Alpha 384.15 on the AX88U, the annoying message:
„FPM Pool 1: invalidtoken 0x21950000 freed" apparently finally on the past.
 
I was't sure if it was gone cos i saw it still but i haven't cleared log then, but if i check now there no invalid tokens anymore, i cleared it like 1 week after updating.
 
With the new Alpha 384.15 on the AX88U, the annoying message:
„FPM Pool 1: invalidtoken 0x21950000 freed" apparently finally on the past.

Great news, however 384.15 is based on 7756 firmware which has a bit of other problems, such as wifi becoming irresponsive or extremely slow... so be aware!
 
Hello Everyone, sorry to ruin the party but I'm running on 384.15 and have the same exact issue.

eb 13 23:44:41 kernel: FPM Pool 0: invalid token 0x02c08000 freed

I suppose is more or less the same issue. Honestly it makes me totally sick. It has started to happen on my previous router AC88U and I thought it was broken. Then I've changed the router and he's doing the same again. Just a reboot of the router is not enough, I have to restart also the Cable.modem.
 
@pirri ...

Have you made a complete factory reset after updating the firmware?

:)
 
@pirri ...

Have you made a complete factory reset after updating the firmware?

:)

No I didn't this time, but I did it with the previous Firmware versions. I have also an AC68U working as an Imesh node, do you think I have to run a factory reset on this router too?
 
Hello Everyone, sorry to ruin the party but I'm running on 384.15 and have the same exact issue.

eb 13 23:44:41 kernel: FPM Pool 0: invalid token 0x02c08000 freed

I suppose is more or less the same issue. Honestly it makes me totally sick. It has started to happen on my previous router AC88U and I thought it was broken. Then I've changed the router and he's doing the same again. Just a reboot of the router is not enough, I have to restart also the Cable.modem.

It's a debug message coming from Broadcom's closed source pieces. Nothing that can be done about these beside just ignoring them.
 
It's a debug message coming from Broadcom's closed source pieces. Nothing that can be done about these beside just ignoring them.

Hi, maybe I shouls post also the following log lines :):

Feb 13 23:44:41 kernel: FPM Pool 0: invalid token 0x02c08000 freed
Feb 13 23:44:46 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=1
Feb 13 23:44:46 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=1025
Feb 13 23:44:46 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=2049
Feb 13 23:45:40 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=3073
Feb 13 23:46:30 wsdd2[1249]: error: wsdd-mcast-v4: wsd_send_soap_msg: send
Feb 13 23:46:30 kernel: port_generic_stop 554 skip turnning off power on eth0 here
Feb 13 23:46:30 kernel: port_generic_open 536 skip turnning on power on eth0 here
Feb 13 23:46:42 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=4097
Again, this happens sporadically but at least once per day. But I'll try to factory reset the router and see if it happens again.
I've noticed also an additional VPN problem, but I will open an additional topic.
 
firmware 386.3_2

Code:
Oct 29 18:57:43 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:58:49 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:58:58 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:01 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:04 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:15 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:15 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:17 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:29 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:35 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 18:59:36 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:00:04 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:00:06 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:00:16 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:00:21 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:00:38 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:00:46 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:00:51 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:10 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:21 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:24 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:38 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:38 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:45 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:53 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:56 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:01:59 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:01 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:13 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:15 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:16 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:18 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:18 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:19 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:19 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:20 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:20 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:20 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:21 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:22 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:24 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:25 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:28 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:35 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:35 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:38 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:39 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:46 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:48 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:48 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:49 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:52 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:53 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:53 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:55 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:59 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:02:59 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:03:01 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Oct 29 19:03:04 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Oct 29 19:03:06 kernel: eth0 (Int switch port: 3) (Logical Port: 3) Link UP 1000 mbps full duplex
 
Any fix for this?
Two days in a row.

firmware 386.3_2

Code:
Jan 27 06:24:07 pppd[2343]: Timeout waiting for PADS packets
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed

Updated to 386.4 to see if the problem will persist
 
Any fix for this?
Two days in a row.

firmware 386.3_2

Code:
Jan 27 06:24:07 pppd[2343]: Timeout waiting for PADS packets
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:07 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed
Jan 27 06:24:08 kernel: FPM Pool 0: invalid token 0x003ff000 freed

Updated to 386.4 to see if the problem will persist

Funny story these errors i may used to have had, i had a rj45 connector from modem to the wan of my router terminated wrong acording to 568b standard first 2 wires where wrong order for me on 1 end, this caused wan instability random disconnects sometimes once a month would drop to 100 mbps, its been rock stable since then, so i would check your wiring.
 
Funny story these errors i may used to have had, i had a rj45 connector from modem to the wan of my router terminated wrong acording to 568b standard first 2 wires where wrong order for me on 1 end, this caused wan instability random disconnects sometimes once a month would drop to 100 mbps, its been rock stable since then, so i would check your wiring.
After updating to 386.4 not a single error...really hope it will stay like that..
But couldn't hurt to try to crimp a new connector if these errors start again.

Thx for the info
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top