After installing the 4.6 kernel and rebooting, lxd-bridge.service failed the same way on two boxes:
May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2112]: Failed to setup lxd-bridge. May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2129]: RTNETLINK answers: Operation not supported May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2129]: Failed to setup lxd-bridge. A simple "brctl addbr foo" does work though, so I guess this happens later on when trying to add veths to it or setting its IP etc. Unfortunately there is no dmesg output about this at all. But after another reboot this curiously succeeded (I verified uname -a that in both cases I was running 4.6.0). I now let one box run with 4.6.0, let's see how long it'll hold up. Another note: With this new kernel, and I think also with the previous 4.4 one, I'm getting an awful lot of "failure to fork" errors, e. g. when trying to run apt-get install; up to the point that right after a fresh boot I can't even install a simple package like "bridge-utils" any more. "ps aux" looks fairly harmless, just 150 lines which includes all the kernel threads. It could of course be that over the course of all the automatic reboots the file system got corrupted in some ways -- but usually another reboot then becomes more lucky and apt-get install (as well as setting up the above bridge) works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531768 Title: [arm64] locks up some time after booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1531768/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
