wpa_supplicant high frequency spam message is flooding system log

Description:

I occationally found(when using journalctl -xe check other problem) that wpa_supplicant is spamming my system logs with messages like:

Apr 22 20:49:21 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=9999 txrate=54000
Apr 22 20:49:21 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=9999 txrate=54000
Apr 22 20:49:22 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=9999 txrate=54000
Apr 22 20:49:22 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=9999 txrate=54000
Apr 22 20:49:23 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-72 noise=9999 txrate=87800
Apr 22 20:49:23 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-72 noise=9999 txrate=87800
Apr 22 20:49:24 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise=9999 txrate=87800
Apr 22 20:49:25 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-69 noise=9999 txrate=117000
Apr 22 20:49:25 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=117000
Apr 22 20:49:26 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=117000
Apr 22 20:49:26 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=117000
Apr 22 20:49:27 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-71 noise=9999 txrate=87800
Apr 22 20:49:28 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-72 noise=9999 txrate=117000
Apr 22 20:49:29 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-65 noise=9999 txrate=117000
Apr 22 20:49:29 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-71 noise=9999 txrate=87800
Apr 22 20:49:30 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=9999 txrate=117000
Apr 22 20:49:33 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-72 noise=9999 txrate=87800
Apr 22 20:49:36 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-64 noise=9999 txrate=58500
Apr 22 20:49:36 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=9999 txrate=58500
Apr 22 20:49:38 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-72 noise=9999 txrate=58500
Apr 22 20:49:38 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=9999 txrate=87800
Apr 22 20:49:39 shilka wpa_supplicant[854]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-70 noise=9999 txrate=87800

Additional info:

After some google work, I found that many people met this problem and the upstream bug fix is already existed: https://w1.fi/cgit/hostap/commit/?id=c330b5820eefa8e703dbce7278c2a62d9c69166a quoted from this post: stackexchange

Steps to reproduce:

  1. check system log with journalctl when wifi is working.