kernel-packages team mailing list archive

["dave.muysson" <dave.muysson@xxxxxxxxx>]

Dan,

  Not sure if this will help or not, but of the 8+ servers we have using
the r3.large instance type, the only two that have encountered the issue
were running MongoDB on them, launched using the numactl tool with the
--interleave=all option set.

Here's the exact launch command used:

exec start-stop-daemon --start --quiet --chuid mongodb --make-pidfile
--pidfile /var/run/mongodb.pid --exec /usr/bin/numactl --
--interleave=all  /usr/bin/mongod --config /etc/mongodb.conf

  I won't pretend to know how numactl interleaves the memory across the
nodes, but I can't help but think high memory usage on these nodes
combined with forced interleaving might be why we hit this issue?

  After weeks of stress testing with your custom kernel, I have yet to
hit this issue again. The synthetic environment I'm using probably isn't
enough to hit this bug. Hopefully your testing with the c4.8xLarge is
more helpful.

-- 
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