Spamming redpine messages in dmesg

Hardware Librem 5
1

Anyone else getting this spammed in their dmesg? Any tips how to further investigate what’s might be wrong?

redpine_91x: Packet Dropped as Key ID not matched with both current and previous Key ID

The only other wi-fi issue I seem to have is that when I ping 1.1.1.1 I usually get 2-8ms response time, but every now and then spikes to 30-150ms for a short while and then goes back again. My router otherwise is an TP-Link Archer C7 v2 running OpenWRT. Using WPA2 or WPA3 does not make any difference. My laptop (ThinkPad Carbon X1 gen2, so not the newest) does not have this behaviour, no dmesg prints and a consistent ping latency of pretty much always 2-3ms with an occasional jump to 5-6ms.

2

Yes, I’m seeing that too. It seems to be a legitimate message, because when it prints I notice extremely slow wifi speeds.

Disconnecting and reconnecting from the network or doing a power cycle of the modem itself seems to fix the issue for a while, but I haven’t tested that systematically.

1 Like
3

I am seeing stuff like…

[165113.761187] redpine_91x: <==== Interface DOWN ====>
[165113.762892] redpine_91x: <==== Interface UP ====>
[165113.762943] redpine_91x: rsi_mac80211_bss_info_changed: Change of ERP INFO: 0
[165113.762952] redpine_91x: rsi_mac80211_bss_info_changed: Sending vap updates....
[165113.835114] redpine_91x: Antenna is changed to 2
[165117.499081] redpine_91x: EAPOL 4 confirm
purism@pureos:~$ sudo dmesg | grep redpine | wc -l
182
purism@pureos:~$
4

redpine_91x: Packet Dropped as Key ID not matched with ...

?

Yes.

I would ping something on your LAN, in order to eliminate other sources of variability.

5

Pinging my router at 192.168.2.1 has pretty much the same result, 2-10ms response time with the occasional jump to 100+ms every 15-30 seconds.

6

Any chance that power save mode is a factor here? Under typical default Access Point settings, a client that goes into power save mode would then incur a delay of up to 102.4 ms, on top of the normal ping latency, plus whatever it takes to get out of power save mode. (The default could also differ between the 2.4 GHz band and the 5 GHz band.) This shouldn’t be a factor because if you are pinging continuously then I wouldn’t expect it to power save but … Also, this applies when it is another device pinging the Librem 5, not the other way round.

Another possibility is that some other system event is occurring on the Librem 5 every 15-30 seconds and that system event is higher priority / is blocking response to the ping.