I recently upgraded to a newer meta-iot2050 commit in my image and since then I more often than not get a kernel panic when running network related commands like sudo systemctl restart networking or sudo ifdown eno1. This seems to be connected with dhcp since running sudo ifdown eno2 on my static network interface works perfectly fine. This also doesn't happen consistently because sometimes it works as if there are no problems at all.
The interfaces in my image are configures like this:
The output of the kernel panic: [kernel_panic.txt](https://github.com/siemens/meta-iot2050/files/14805649/kernel_panic.txt)
Any ideas as to why this happens would be appreciated!
Hello there,
I recently upgraded to a newer meta-iot2050 commit in my image and since then I more often than not get a kernel panic when running network related commands like
sudo systemctl restart networkingorsudo ifdown eno1. This seems to be connected with dhcp since runningsudo ifdown eno2on my static network interface works perfectly fine. This also doesn't happen consistently because sometimes it works as if there are no problems at all.The interfaces in my image are configures like this:
allow-hotplug eno1 iface eno1 inet dhcp
The loopback network interface
auto lo iface lo inet loopback
allow-hotplug eno2 iface eno2 inet static address 192.168.200.10 netmask 255.255.255.0