The newer kernel may have some change/fix that prevents this bug, as I haven't seen any reports of this (from google, at least) on any other kernel. Plus, the unusual requirement of the memory having to end at not a multiple of 2M.
> But the “Node 0 Normal” zone, judging from (start_pfn, start_pfn+spanned) > spans 100000000-f18000000. > The machine in question is a c4.8xlarge in EC2. Awesome, I'll set up a vm with that flavor to see if I can reproduce this, or at least reproduce the problematic zone setup. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1497428 Title: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968 Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: The kernel triggers a BUG when it finds it is in move_freepages() but the start and end pfns for the move are in different zones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1497428/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
