Closed anabolyc closed 4 months ago
I thought we already agreed on the fact that telnet isn't working, but more information was needed to possibly fix the telnet issue 😉
@anabolyc
Thank you for the hint. Everything worked now using your docker command.
After enabling telnet the system crashed again. The reason is a stack overflow in task Tmr Svc. Attached you find the output of "idf.py monitor" containing the backtrace.
@philippe44
I think you are one of the few persons with enough insight to fix this. Looking at the backtrace, do you have a clue what can be done?
A stack overflow on the timer service would indicate that there's an issue with the amount of memory dedicated to the... Timer service. This is something that would need fixed in the sdkconfig.
I see that the default values were used CONFIG_ESP_TIMER_TASK_STACK_SIZE=3584 But it might require some fine tuning on that platform
We can fix it by increasing the stack but it is precious internal ram AFAIR. The esp-idf timer calls any callback registered under timer service using its own task (not an isr) stack. This is why one has to be careful what we do in that callback and also because it's a shared task for all callbacks, best is to either something really quick or send a message to wake up another task. I'll have to verify all the routines that we register for timer services.
Describe the bug
hey folks, I'm testing squeezelite-esp32 with the ESP32-S3 board built with espidf v.4.4.7 Took me some time to prepare working sdkconfig, but code builds and runs, I was able to configure wifi and find device in the network. However only slim-proto seems to work as expected. Neither scpot nor airplay works as it should.
Preliminary Information
Hardware Details
Please describe your hardware setup:
Airplay Logs
Airplay connects fine, but as soon as audio starts, errors are fired into the log. Speakers seem to issue occasional sounds, but you'd not recognize any audio of it.
Cspot Logs
Cspot crashes as soon as I connect the client to the device
Issue Description