samples: net: civetweb: websocket_server #46743
Assignees
Labels
area: civetweb
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Comments
mbolivar-nordic
added a commit
to mbolivar-nordic/zephyr
that referenced
this issue
Jun 21, 2022
This code has gone unmaintained and bugs continue to be reported against it. We do not have the resources as a project to maintain this in "odd fixes" mode, and nobody has stepped up to maintain it [1], so sadly this must be removed for now. If anyone would like to see civetweb supported in upstream Zephyr again, they are welcome to add it back, as long as they promise to maintain it going forward. Many thanks to everyone who has contributed to civetweb support in Zephyr while it was here. So long and thanks for all the fish. Fixes: zephyrproject-rtos#45807 Fixes: zephyrproject-rtos#43910 Fixes: zephyrproject-rtos#34226 Fixes: zephyrproject-rtos#46743 [1] https://lists.zephyrproject.org/g/devel/message/8466 Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
mbolivar-nordic
added a commit
that referenced
this issue
Jun 22, 2022
This code has gone unmaintained and bugs continue to be reported against it. We do not have the resources as a project to maintain this in "odd fixes" mode, and nobody has stepped up to maintain it [1], so sadly this must be removed for now. If anyone would like to see civetweb supported in upstream Zephyr again, they are welcome to add it back, as long as they promise to maintain it going forward. Many thanks to everyone who has contributed to civetweb support in Zephyr while it was here. So long and thanks for all the fish. Fixes: #45807 Fixes: #43910 Fixes: #34226 Fixes: #46743 [1] https://lists.zephyrproject.org/g/devel/message/8466 Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
|
"Fixed" by the removal of civetweb. See #46746 for more details. Thanks for taking the time to file an issue and sorry for the inconvenience. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
While developing a new ethernet driver for Intel Cyclone V SoC DevKit board, we were testing the example located in https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/net/civetweb/websocket_server
When the message is too long, the Zephyr kernel has problem:
[00:00:54.132,000] os: ***** MPU FAULT *****
[00:00:54.132,000] os: Stacking error (context area might be not valid)
[00:00:54.132,000] os: Data Access Violation
[00:00:54.132,000] os: MMFAR Address: 0x2000ceb8
[00:00:54.132,000] os: r0/a1: 0x121bcb9f r1/a2: 0x4e7439c2 r2/a3: 0x2
[00:00:54.132,000] os: r3/a4: 0xe45754cc r12/ip: 0xcc2d83d0 r14/lr: 0xd
[00:00:54.132,000] os: xpsr: 0xb7aec000
[00:00:54.132,000] os: Faulting instruction address (r15/pc): 0x01a05abf
[00:00:54.132,000] os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:54.132,000] os: Current thread: 0x20005438 (unknown)
[00:00:54.219,000] os: Halting system
We validated this problem in two boards cyclonev_socdk and nucleo_f429zi
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The message is to be clearly passed on the webserver page without errors on the board.
The text was updated successfully, but these errors were encountered: