rf95 stuck in tx mode sometimes about firmware HOT 6 CLOSED

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/bin-v0-2-3-on-ttgo-t-beamv1-0/101/3

from firmware.

I just saw a related bug happen on one of my boards 0xb4:

pressing
Trigger powerFSM 1
Transition powerFSM transition=Press, from=ON to=ON
Sending network ping to 0xff, with position=1, wantReplies=1
Update DB node 0xb4, rx_time=1587163015
Providing time to mesh 1587163015
Deleting old broadcast record 0
Adding broadcast record for fr=0xb4,to=0xff,id=59
Sending packet via interface fr=0xb4,to=0xff,id=59
immediate send on mesh fr=0xb4,to=0xff,id=59
(txGood=6,rxGood=8,rxBad=2)
Setting fast framerate
Setting idle framerate
fix type 3
fix type 3
new gps pos lat=37.521016, lon=-122.309064, alt=134
got gps notify
Update DB node 0xb4, rx_time=1587163034
ERROR! Bug! Tx packet took too long to send, forcing radio into rx mode
NOTE! Recording critical error 1, address=0
fix type 3
new gps pos lat=37.520912, lon=-122.309194, alt=133
got gps notify
Update DB node 0xb4, rx_time=1587163064
fix type 3

from firmware.

this failure has the same root cause (TBD) I think

from firmware.

on sleep entry we are sitting in rxmode (not receiving). but with something waiting in the tx queue.

canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
canSleep, mode=4, isRx=0, txEmpty=0, txGood=32
NOTE! Recording critical error 2, address=0
Setting bluetooth enable=0

from firmware.

yay! Fixed (I'm almost sure, it ran for a few hours with a stress test of doing lots of extra sends)

from firmware.

This issue has been mentioned on Meshtastic. There might be relevant details there:

https://meshtastic.discourse.group/t/device-code-release-announcements/32/18

from firmware.