From: Dave Hansen <dave.hansen@intel.com>
To: Richard Davies <richard@arachsys.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: Unnecessary mass OOM kills on Linux 3.11 virtualization host
Date: Mon, 28 Oct 2013 11:13:27 -0700 [thread overview]
Message-ID: <526EA947.7060608@intel.com> (raw)
In-Reply-To: <20131028082825.GA30504@alpha.arachsys.com>
On 10/28/2013 01:28 AM, 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.
--
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>
next prev parent reply other threads:[~2013-10-28 18:14 UTC|newest]
Thread overview: 12+ 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-25 10:39 ` Richard Davies
2013-10-28 8:28 ` Richard Davies
2013-10-28 18:13 ` Dave Hansen [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=526EA947.7060608@intel.com \
--to=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard@arachsys.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).