On 01/25/2014 04:47 PM, Dan Merillat wrote:
I'm trying to track this down - this started happening without changing the
kernel in use, so probably
a corrupted filesystem. The symptoms are that all memory is suddenly used by no
apparent source. OOM
killer is invoked on every task, still can't
I'm trying to track this down - this started happening without changing
the kernel in use, so probably
a corrupted filesystem. The symptoms are that all memory is suddenly used
by no apparent source. OOM
killer is invoked on every task, still can't free up enough memory to
continue.
I
Dan Merillat posted on Sat, 25 Jan 2014 16:47:35 -0500 as excerpted:
I'm trying to track this down - this started happening without changing
the kernel in use, so probably a corrupted filesystem. The symptoms are
that all memory is suddenly used by no apparent source. OOM killer is
invoked
On Jan 25, 2014, at 2:47 PM, Dan Merillat dan.meril...@gmail.com wrote:
[ 1219.366168] ntpd invoked oom-killer: gfp_mask=0x201da, order=0,
oom_score_adj=0
[ 1219.366270] CPU: 1 PID: 5479 Comm: ntpd Not tainted 3.12.8-00848-g97f15f1
#2
This and the whole call track don't have anything in
Chris Murphy posted on Tue, 28 Jan 2014 20:57:45 -0700 as excerpted:
On Jan 25, 2014, at 2:47 PM, Dan Merillat dan.meril...@gmail.com
wrote:
[ 1219.366168] ntpd invoked oom-killer: gfp_mask=0x201da, order=0,
oom_score_adj=0 [ 1219.366270] CPU: 1 PID: 5479 Comm: ntpd Not tainted
I'm trying to track this down - this started happening without changing the
kernel in use, so probably
a corrupted filesystem. The symptoms are that all memory is suddenly used by no
apparent source. OOM
killer is invoked on every task, still can't free up enough memory to continue.
When it
