From: Bokhan Artem <art@eml.ru>
To: Borislav Petkov <bp@alien8.de>, linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at /build/buildd/linux-2.6.32/mm/mempolicy.c
Date: Wed, 05 Dec 2012 22:53:21 +0700 [thread overview]
Message-ID: <50BF6DF1.4080802@eml.ru> (raw)
In-Reply-To: <20121205155357.GB12119@liondog.tnic>
On 05.12.2012 22:53, Borislav Petkov wrote:
> On Wed, Dec 05, 2012 at 10:22:08PM +0700, Bokhan Artem wrote:
>> Hello.
>>
>> We have several servers with mongodb running. Each server has
>> several mongodb instances. Mongodb dataset is larger then availiable
>> memory (mongodb uses memory-mapped files for all disk I/O).
>> 2.6.32 and 2.6.38 kernels periodically crash and crash happens only
>> with mongodb servers.
>>
>> 2.6.38's trace is in attachment.
>> For 2.6.32 I only have "kernel BUG at
>> /build/buildd/linux-2.6.32/mm/mempolicy.c:1489!"
> Can you reproduce this with the current upstream kernel 3.7-rc8? If no,
> then you should complain to the ubuntu people or whoever provides your
> kernels.
>
We will try.
next prev parent reply other threads:[~2012-12-05 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 15:22 kernel BUG at /build/buildd/linux-2.6.32/mm/mempolicy.c Bokhan Artem
2012-12-05 15:53 ` Borislav Petkov
2012-12-05 15:53 ` Bokhan Artem [this message]
2012-12-05 16:46 ` Devendra C
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=50BF6DF1.4080802@eml.ru \
--to=art@eml.ru \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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 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).