22.05-RC high CPU load

[renegade]

@stephenw10
Yeah, you are right. I have to improve that. Unfortunately the device is in a quite warm environment.

And yes, that's what I can see on my installation. Same behaviour.
thanks for confirming, Steven.

[dennypage]

FWIW, I've seen similar.

Hasn't resulted in a problem though.

[stephenw10]

Also running pfBlocker? Does it start after some time, not immediately?

[dennypage]

@stephenw10 Yes, running pfBlockerNG-devel.

At first I thought I noticed that it didn't start right after boot, but I didn't investigate sufficiently.

I just rebooted and checked carefully, and you are right, CPU starts ramping up approximately 2 minutes after boot is complete.

[dennypage]

@stephenw10 Without rebooting, stopping the pfb_filter returns the cpu to normal levels.

Restarting pfb_filter cause cpu to return to higher levels after approximately 2 minutes and 30 seconds..

[renegade]

I noticed that there is a new Snapshot version of the 22.05 RC this morning.
Is it fixed already? Or has pfblocker maybe to fix it?

[stephenw10]

It is not fixed as far as I know. Tracking it here: https://redmine.pfsense.org/issues/13154

Add any additional details you may uncover there.

Steve

[dennypage]

@stephenw10, I've updated the redmine issue with a temporary fix. I make no representation that this fix is the best approach.

@BBcan177, please take a look. Thanks.

[stephenw10]

Nice. Looks like work is already in progress here: https://redmine.pfsense.org/issues/13156

[dennypage]

@stephenw10 Well shucks. Seeing that would have saved me a bunch of work. I guess I need to spend more time spelunking redmine.

[stephenw10]

Yup I missed that too. Or at least I failed to realise the root cause was the same.

Still when you independently come up with the same fix that's always a good sign.

Working for me here on 2.7.

Steve

[drewsaur]

Thank you all and @BBcan177 for the simple patch, because I was about to make a long post looking for help, and the little edit to line 4139 solved my CPU load issues with 22.05 completely.

I think this fix should be made more prominent - I am not using a 22.05 development snapshot, but rather 22.05 final, and I found this thread via a search and not via a browse of the forums. I feel lucky to have found it.