Need help identifying an error message

Matt_Reeser · August 29, 2015, 12:05am

We had an AP loose it's GPS sync.

Software version 2.4.2

GPS is up to date with version AXN_1.51_2838

No other AP at the site lost GPS sync.

This is from the log. Any ideas?

Aug 28 11:50:08 Park_ePMP04 kernel: GPS Sync Lost. (17:50:08:676658)
Aug 28 11:50:08 Park_ePMP04 kernel: All STAs disassociated. IEEE80211_REASON_TDD_STOP (20)
Aug 28 11:52:08 Park_ePMP04 kernel: Reseting On-Board GPS.......
Aug 28 11:52:08 Park_ePMP04 kernel: $PGACK,101*42
Aug 28 11:52:08 Park_ePMP04 kernel: $PGACK,201*41
Aug 28 11:52:08 Park_ePMP04 kernel: $PMTK011,MTKGPS*08
Aug 28 11:52:08 Park_ePMP04 kernel: $PMTK010,001*2E
Aug 28 11:56:08 Park_ePMP04 kernel: GPS Sync Restored. (17:56:08:183566)
Aug 28 11:59:07 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 11:59:07 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2269 rxstate_18:0 no_rxintr_count:0 rxeol:3083 rxorn:8
Aug 28 12:04:11 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 12:04:11 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2270 rx
state_18:0 no_rxintr_count:0 rxeol:3084 rxorn:8

I keep getting this message in the log.

Aug 28 14:06:48 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 14:06:48 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2279 rxstate_18:0 no_rxintr_count:0 rxeol:3093 rxorn:8
Aug 28 14:07:05 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 14:07:05 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2280 rxstate_18:0 no_rxintr_count:0 rxeol:3094 rxorn:8
Aug 28 14:07:53 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 14:07:53 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2281 rxstate_18:0 no_rxintr_count:0 rxeol:3095 rxorn:8
Aug 28 14:52:26 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 14:52:26 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2282 rxstate_18:0 no_rxintr_count:0 rxeol:3096 rxorn:8
Aug 28 15:42:46 Park_ePMP04 kernel: Adding WDS entry for 1c:b7:2c:7c:1a:44, through ni=00:04:56:c8:c7:fe 
Aug 28 16:03:24 Park_ePMP04 kernel: Adding WDS entry for 94:10:3e:fa:3e:f4, through ni=00:04:56:c8:95:7c 
Aug 28 16:21:39 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 16:21:39 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2283 rxstate_18:0 no_rxintr_count:0 rxeol:3097 rxorn:8
Aug 28 16:25:41 Park_ePMP04 kernel: Flags 0, Scheduler Mode 0
Aug 28 16:25:41 Park_ePMP04 kernel: **RX stuck: issue1; workaround, HAL restart! badkey_wbufdrop:2284 rxstate_18:0 no_rxintr_count:0 rxeol:3098 rxorn:8

Is the AP telling me the work around is to reboot the AP?

Chris_Bay · August 29, 2015, 2:26am

You can likely increase your GPS sync hold off time to mask the problem until you’ve resolved the problem correctly also. That setting is configuration > radio, and the very bottom of the page, set it to a very large time to allow your ap to recover that error until the problems worked out.

I haven’t came across that particular issue before, we did a long time ago have a similar problem with a sync pipe and the root cause was low voltage to the device, changing the power supply in that instance fixed it. Probably not the case for you though

LBNL · August 17, 2018, 2:21pm

Sorry to dig up an old thread but we're also seeing this on a connectorised radio:

Sep  3 01:49:14 s2pp2 kernel: [179359.650000] **RX stuck: issue2; workaround, HAL restart! badkey_wbufdrop:115 rxstate_18:33 no_rxintr_count:4708 rxeol:4839 rxorn:231
Sep  3 01:51:43 s2pp2 kernel: [179508.200000] SlotTime 9, AIFS 1, GTT 100, SIFS 14, CCA Threshold -47
Sep  3 01:51:43 s2pp2 kernel: [179508.200000] cca init -> weak = 2	strong = 10 -> done
Sep  3 01:51:43 s2pp2 kernel: [179508.200000] **RX stuck: issue2; workaround, HAL restart! badkey_wbufdrop:115 rxstate_18:33 no_rxintr_count:4709 rxeol:4840 rxorn:231

Radio uptime is low, fw version is 3.5.1

Anyone able to help please?

LBNL · December 15, 2018, 2:30pm

And anther PtP link on 2.6.1:

Dec 15 14:10:08 s04pp1 kernel: cca init -> weak = 2 strong = 10 -> done
Dec 15 14:10:08 s04pp1 kernel: **RX stuck: issue2; workaround, HAL restart! badkey_wbufdrop:0 rxstate_18:0 no_rxintr_count:31 rxeol:29 rxorn:0
Dec 15 14:10:08 s04pp1 kernel: SlotTime 9, AIFS 1, GTT 100, SIFS 14, CCA Threshold -53
Dec 15 14:10:08 s04pp1 kernel: cca init -> weak = 2 strong = 10 -> done
Dec 15 14:10:08 s04pp1 kernel: **RX stuck: issue2; workaround, HAL restart! badkey_wbufdrop:0 rxstate_18:0 no_rxintr_count:32 rxeol:30 rxorn:0
Dec 15 14:10:09 s04pp1 kernel: SlotTime 9, AIFS 1, GTT 100, SIFS 14, CCA Threshold -53
Dec 15 14:10:09 s04pp1 kernel: cca init -> weak = 2 strong = 10 -> done
Dec 15 14:10:09 s04pp1 kernel: **RX stuck: issue2; workaround, HAL restart! badkey_wbufdrop:0 rxstate_18:0 no_rxintr_count:33 rxeol:31 rxorn:0
Dec 15 14:10:09 s04pp1 kernel: SlotTime 9, AIFS 1, GTT 100, SIFS 14, CCA Threshold -53
Dec 15 14:10:09 s04pp1 kernel: cca init -> weak = 2 strong = 10 -> done
Dec 15 14:10:09 s04pp1 kernel: **RX stuck: issue2; workaround, HAL restart! badkey_wbufdrop:0 rxstate_18:0 no_rxintr_count:34 rxeol:32 rxorn:0
Dec 15 14:10:09 s04pp1 kernel: SlotTime 9, AIFS 1, GTT 100, SIFS 14, CCA Threshold -53
Dec 15 14:10:09 s04pp1 kernel: cca init -> weak = 2 strong = 10 -> done
Dec 15 14:10:09 s04pp1 kernel: **RX stuck: issue2; workaround, HAL restart! badkey_wbufdrop:0 rxstate_18:0 no_rxintr_count:35 rxeol:33 rxorn:0
Dec 15 14:10:09 s04pp1 kernel: SM[00:04:56:f8:73:9b] aid=1 disassociated. Reason: COMMUNICATION LOST
Dec 15 14:10:09 s04pp1 hostapd: ath0: STA 00:04:56:f8:73:9b IEEE 802.11: disassociated
Dec 15 14:18:01 s04pp1 hostapd: ath0: STA 00:04:56:f8:73:9b IEEE 802.11: associated
Dec 15 14:18:01 s04pp1 hostapd: ath0: STA 00:04:56:f8:73:9b RADIUS: starting accounting session 55E4EA8A-0000000F
Dec 15 14:18:01 s04pp1 hostapd: ath0: STA 00:04:56:f8:73:9b WPA: pairwise key handshake completed (RSN)