From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Ortwin Glück" <odi@odi.ch>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG at mm/memory.c
Date: Thu, 19 Jun 2014 19:52:05 +0300 [thread overview]
Message-ID: <20140619165205.GA26761@node.dhcp.inet.fi> (raw)
In-Reply-To: <53A3102E.2030602@odi.ch>
On Thu, Jun 19, 2014 at 06:30:38PM +0200, Ortwin Glück wrote:
> Hi,
>
> I was hitting a BUG while running a couple of qemu 2.0 on a 3.15.0 kernel. KSM was running. This box uses NUMA with two E5 6-core Xeons.
>
> Linux toaster 3.15.0 #1 SMP PREEMPT Thu Jun 12 14:05:12 CEST 2014 x86_64 Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz GenuineIntel GNU/Linux
>
> Jun 17 16:59:47 toaster kernel: ------------[ cut here ]------------
> Jun 17 16:59:47 toaster kernel: kernel BUG at mm/memory.c:3924!
http://marc.info/?l=linux-kernel&m=140319579508104&w=2
--
Kirill A. Shutemov
next prev parent reply other threads:[~2014-06-19 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 16:30 BUG at mm/memory.c Ortwin Glück
2014-06-19 16:52 ` Kirill A. Shutemov [this message]
2014-06-20 10:59 ` Ortwin Glück
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=20140619165205.GA26761@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=odi@odi.ch \
/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