From: Richard Davies <richard@arachsys.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: Unnecessary mass OOM kills on Linux 3.11 virtualization host
Date: Mon, 28 Oct 2013 18:23:09 +0000 [thread overview]
Message-ID: <20131028182309.GA21822@alpha.arachsys.com> (raw)
In-Reply-To: <526EA947.7060608@intel.com>
Dave Hansen wrote:
> Richard Davies wrote:
> > I further attach some other types of memory manager errors found in the
> > kernel logs around the same time. There are several occurrences of each, but
> > I have only copied one here for brevity:
> >
> > 19:18:27 kernel: BUG: Bad page map in process qemu-system-x86 pte:00000608 pmd:1d57fd067
>
> FWIW, I took a quick look through your OOM report and didn't see any
> obvious causes for it. But, INMHO, you should probably ignore the OOM
> issue until you've fixed these "Bad page map" problems. Those are a
> sign of a much deeper problem.
Thanks! What investigation should I do for these? It is on stock 3.11.3.
Richard.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Richard Davies <richard@arachsys.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: Unnecessary mass OOM kills on Linux 3.11 virtualization host
Date: Mon, 28 Oct 2013 18:23:09 +0000 [thread overview]
Message-ID: <20131028182309.GA21822@alpha.arachsys.com> (raw)
In-Reply-To: <526EA947.7060608@intel.com>
Dave Hansen wrote:
> Richard Davies wrote:
> > I further attach some other types of memory manager errors found in the
> > kernel logs around the same time. There are several occurrences of each, but
> > I have only copied one here for brevity:
> >
> > 19:18:27 kernel: BUG: Bad page map in process qemu-system-x86 pte:00000608 pmd:1d57fd067
>
> FWIW, I took a quick look through your OOM report and didn't see any
> obvious causes for it. But, INMHO, you should probably ignore the OOM
> issue until you've fixed these "Bad page map" problems. Those are a
> sign of a much deeper problem.
Thanks! What investigation should I do for these? It is on stock 3.11.3.
Richard.
next prev parent reply other threads:[~2013-10-28 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131024225718.GA4363@alpha.arachsys.com>
2013-10-24 22:43 ` Unnecessary mass OOM kills on Linux 3.11 virtualization host Richard Davies
2013-10-24 22:43 ` Richard Davies
2013-10-25 10:39 ` Richard Davies
2013-10-25 10:39 ` Richard Davies
2013-10-28 8:28 ` Richard Davies
2013-10-28 8:28 ` Richard Davies
2013-10-28 18:13 ` Dave Hansen
2013-10-28 18:13 ` Dave Hansen
2013-10-28 18:23 ` Richard Davies [this message]
2013-10-28 18:23 ` Richard Davies
2013-11-13 11:18 ` Alin Dobre
2013-11-13 12:09 ` Cyrill Gorcunov
2013-11-13 12:35 ` Alin Dobre
2013-11-13 13:19 ` Cyrill Gorcunov
2013-11-14 9:50 ` Alin Dobre
2013-11-14 10:12 ` David Rientjes
2013-11-14 10:14 ` Alin Dobre
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131028182309.GA21822@alpha.arachsys.com \
--to=richard@arachsys.com \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.