On 2021-07-26 17:09, Petr Štetiar wrote: > Petr Štetiar <yn...@true.cz> [2021-07-26 17:01:32]: > >> This reverts commit 089efd61e9a6cdc0ea39c184d37bc8ebbe03175c as it >> breaks LAN network on at least mvebu/turris-omnia device. >> >> Confirmed-by: Josef Schlehofer <pepe.schleho...@gmail.com> >> Signed-off-by: Petr Štetiar <yn...@true.cz> >> --- >> >> I've discovered this today in the morning in my testbed where I perform daily >> runtime tests of initramfs images on several devices, where images/tests for >> snapshot and 21.02-SNAPSHOT failed on turris-omnia device. > > Sorry, forgot to provide more detials. The problem is with initialization of > LAN network, where the interface readiness is tested by following command: > > ifstatus lan | jsonfilter -qe "@.up" > > then the LAN network availability is tested with simple `ping -c1 192.168.1.2` > command which timeouts. This is pristine image with no config changes, so the > device has 192.168.1.1/24 network config and the other end 192.168.1.2/24. > > Console logs are available: > > snapshot > https://gitlab.com/ynezz/openwrt-device-runtime-testing/-/jobs/1451323563/artifacts/file/console_turris-omnia-initramfs.txt > 21.02 > https://gitlab.com/ynezz/openwrt-device-runtime-testing/-/jobs/1451222403/artifacts/file/console_turris-omnia-initramfs.txt Fixed the regression in master and 21.02, sorry about the mess. For some reason, it did not trigger in my configurations...
- Felix _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel