The only fix I can see for this is to make sure linaro-media-create is always creating a swapfile when installing to certain known low-memory targets. We can do that one of two ways; we can make a default swap size part of the board config info (and have an override command-line option to disable, perhaps --no-swap?), or we can just update the documentation to mention how much memory is needed for a given image to run and expect users to set appropriate swap themselves. Reassigning to linaro-image-tools for consideration of the first option.
(BTW, Tom, was there any particular evidence that fsck.ext3 was using more memory than reasonable here? Perhaps we should also be filing a bug task against e2fsprogs.) ** Project changed: linaro => linaro-image-tools -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680650 Title: fsck causes oops on xm because of no swap -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
