From: Jiri Slaby <jslaby@suse.cz>
To: Michel Lespinasse <walken@google.com>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Jiri Slaby <jirislaby@gmail.com>
Subject: Re: BUG at mm/huge_memory.c:1428!
Date: Fri, 14 Sep 2012 21:28:33 +0200 [thread overview]
Message-ID: <50538561.8030505@suse.cz> (raw)
In-Reply-To: <CANN689E0SaT9vaBb+snwYrP728GjZhRj7o7T4GoNfQVY7sBr7Q@mail.gmail.com>
On 09/14/2012 12:46 AM, Michel Lespinasse wrote:
> On Thu, Sep 13, 2012 at 11:14 AM, Jiri Slaby <jslaby@suse.cz> wrote:
>> Hi,
>>
>> I've just get the following BUG with today's -next. It happens every
>> time I try to update packages.
>>
>> kernel BUG at mm/huge_memory.c:1428!
>
> That is very likely my bug.
>
> Do you have the message that should be printed right above the bug ?
> ( printk(KERN_ERR "mapcount %d page_mapcount %d\n",
> mapcount, page_mapcount(page));
> )
Unfortunately no. And I cannot reproduce anymore :(...
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-09-14 19:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 18:14 BUG at mm/huge_memory.c:1428! Jiri Slaby
2012-09-13 22:46 ` Michel Lespinasse
2012-09-14 19:28 ` Jiri Slaby [this message]
2012-09-17 15:39 ` Jiri Slaby
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=50538561.8030505@suse.cz \
--to=jslaby@suse.cz \
--cc=aarcange@redhat.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=walken@google.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).