Looking at the whole thing more in depth, this turns out to be a very very very long winded way of the kernel telling us that something tried to allocate 128K of continuous memory and failed (which includes a stack trace and a dump of memory info). It does not say OOPS actually. As far as I see this is likely triggered by virtnet_poll() which tries to pull in data from the virtual network. It does so using GFP_ATOMIC which allows for failure without waiting but does not automatically set the flag to suppress warnings like this. Probably that might be improved. The code AFAICS is prepared to handle the allocation failure and there does not seem to be an immediate crash involved. In this report there is one statement about a hung installation. In the other confirmations I have not seen indication whether the install proceeds or not. There is not much more I can say from the posted messages. And the jenkins links seem to go to 404 for me.
** Summary changed: - 20110531 i386 server ISO: kernel OOPS during install + 20110531 i386 server ISO: order 5 allocation failure during install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790712 Title: 20110531 i386 server ISO: order 5 allocation failure during install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790712/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
