-
Notifications
You must be signed in to change notification settings - Fork 817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guru Meditation Error: Core 1 panic'ed - core dump after 2 days of error free operation. #620
Comments
You may try to erase the flash before a new upload to see if it is still core dumping. Could you post your configuration used (env definition from platformio.ini) and user_config.h if you modified it? Could you indicate your router model and eventually try with your smartphone as an internet AP? Were you on development branch or on BLE refactor PR branch? |
platformio.ini: No customisation other than uncommenting the
User_config.h and changed the time_avoid_duplicate value to 150ms: Router Model: UniFi AP-nanoHD (small business router with strong,reliable Wifi connection) Version: Release 0.9.4beta Github Pre Release ESP32 Logs with RF module attached (core dump happens):
Logs without RF module attached (core dump does not occur)
|
This message appears when Do you have something connected to |
good point but not that I am aware.. I have:
No special setup, this is complete stock as per documentation. Figured I'd give that a go before customising it. (usb connection not shown below) I have checked the connections. The RF module works perfectly on Raspberry Pi. |
You can see that in the compatibility list.
This can be of course an issue, I have the case of if connected to an USB Hub the ESP reset continuously.
Try to change the value of TRIGGER_PIN to 26 to see if you get the same behaviour. |
@danobot did you got the opportunity to test with another |
Yes, changing the TRIGGER_PIN allowed me to set up the ESP32 and had it run for 5 days. Last night, it crashed again. Havent checked the logs why it crashed this time yet. |
Thanks for the PR and fix. |
I have found something else, I think that there is an issue with the interrupt handling of RCSwitch library in ESP32 context. I'm currently investigating it. The core dump occur especially when the Wifi is disconnected. |
So as to reproduce:
The interesting sentence is The issue occurs only when using rcswitch library, irremoteESP8266 doesn't generate this problem when using esp32dev-ir. So the issue seems to be related with interrupts usage (the 2 libraries above use interrupts to detect the coming signals), we can also see that IRRemote ESP8266 user had also this kind of issue. Let's analyse RCSwitch code: I've found an interesting comment saying that the variable used in the interrupt should be put into DRAM (thanks @atanisoft). So I tried to add DRAM_ATTR to the different varaibles accessed by the interrupts functions. I'm going to push the modifications to RCSwitch repositories. |
so as to avoid core dump when using RCSwitch on ESP32 and having wifi disconnection #620
And replace ICACHE_RAM_ATTR by IRAM_ATTR for ESP32, so as to avoir core dump when using in conjunction with Wifi 1technophile/OpenMQTTGateway#620
Correction pushed into RCSwitch repositories |
And replace ICACHE_RAM_ATTR by IRAM_ATTR for ESP32, so as to avoir core dump when using in conjunction with Wifi 1technophile/OpenMQTTGateway#620
Describe the bug
I configured this on a new ESP32 dev board using
v0.9.4beta
which I read somewhere contians stability improvements for esp32. (The non beta version didn't work at all for me).The esp with OMG was running fine for 2 days. Last night it stopped working altogether at 2am. WHen i plugged in to check serial logs, the device had reset itself and lost the wifi configuration entering the wifi AP loop.
Core dump printed (full log at the end):
To Reproduce
Not sure how to reproduce it because it was working fine for 2 days, then stopped working and now I am unable to even set it up on ESP32 as it keeps coredumping due to
Meditation Error
Expected behavior
Not to cause this kind of low Level error. I'm a software engineer myself and this really stumps me. What is wrong? ESP32 is supported and many people are using it in a production environment. I've had so many issues, same with esp8266.
Do let me know how I can help with this.
Screenshots
Na
Environment (please complete the following information):
Additional context
I tried this on ESP8266 and the logs shows MQTT connection error because the "omg" user was supplied, which is not configured in MQTT server. AFter finding this out, checked the ESP32 again and omitted the MQTT user in configuration, unfortunately no luck.
omitting the MQTT user on ESP32 as deployment to ESP8266 showed MQTT errors in the logs
The text was updated successfully, but these errors were encountered: