Dear NXP Community,
we use i.MX7 processors in combination with Yocto Project (Release 5.2 (walnascar)).
Last years we used the community kernel [linux-fslc](https://github.com/Freescale/linux-fslc).
Since security requirements getting tighter, we decided to switch to official nxp kernel [linux-imx](https://github.com/nxp-imx/linux-imx) (lf-6.12.y).
Problem: Beside others, we use [websocketd](https://github.com/joewalnes/websocketd) with this example [yocto-recipe](https://layers.openembedded.org/layerindex/recipe/152495/) and it worked well with freescale linux-fslc (tested on different versions). Websocketd is mainly written in go.
When running linux-imx we observer sporadic crashes like:
runtime: s.allocCount= 991 s.nelems= 992
fatal error: s.allocCount != s.nelems && freeIndex == s.nelems
goroutine 121 gp=0x29465a8 m=3 mp=0x2839008 [running]:
runtime.throw({0x836e6b, 0x31})
runtime/panic.go:1101 +0x38 fp=0x284995c sp=0x2849948 pc=0x53c8a8
......
2025/07/17 10:10:14 http: panic serving 127.0.0.1:41334: runtime error: invalid memory address or nil pointer dereference
goroutine 72 [running]:
net/http.(*conn).serve.func1()
net/http/server.go:1947 +0xf0
panic({0x876cd8, 0xa535f8})
runtime/panic.go:792 +0x110
We don´t think that these are bugs inside the application (since it works well on linux-fslc - device tree and kernel config are the same).
Is there anything we missed during the switch over from linux-fslc to linux-imx (MMU, DMA, thread-model ...)?
Thanks in advance and best regards,
Tommy
