Open avbentem opened 6 years ago
So far it has reported this error, and rebooted after that, 522 times since installing 1.0.5 on July 17th (which is 70 days ago). Often, if not always, the assert is preceded by (a partial) LORA: Kick LoRa module with ACK after not acked it for 60s
, but not every such message yields the failing assert.
The statistics have improved a little bit: so far it rebooted for this reason 1,070 times since installing 1.0.5 on July 17th, which is 197 days ago. It has been receiving far fewer packets in the last months as I switched off some test node, but the assert
is not (always) related to recent LoRa activity, so maybe the number of packets doesn't affect this at all. It's not happening every day, but a few days even have 20 reboots or more:
23 2018-07-23
20 2018-08-10
26 2018-09-22
20 2018-11-14
35 2018-12-13
22 2018-12-17
29 2019-01-20
This is a bug report
What do you want to do? What do you expect?
Expecting a proper gateway to not show software or hardware errors in the log.
What steps did you take? (Give as many details as possible so that we can reproduce it)
Gateway is just running and accepting LoRa packets, configured for both a Ziggo ethernet and XS4ALL WiFi connection.
What went wrong? What is missing?
While the gateway is running just fine, it suddenly reports something like the following and reboots:
I've seen this message and its reboot 225 times since I upgraded to 1.0.5 on July 17th. In 3 occasions the gateway did not recover from the reboot, but that's covered in #8.
What firmware is running on your gateway?
1.0.5 with the factory bootloader.
What do the logs show?
Timestamps added by my own monitoring:
Any Screenshots or Photos?
N/A
Do you think you can try to fix this yourself and submit a pull request?
No.