From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: mm: kernel BUG at mm/huge_memory.c:1440!
Date: Fri, 10 Jan 2014 19:00:16 +0200 [thread overview]
Message-ID: <20140110170016.GA5179@node.dhcp.inet.fi> (raw)
In-Reply-To: <52C819E2.8090509@oracle.com>
On Sat, Jan 04, 2014 at 09:25:38AM -0500, Sasha Levin wrote:
> On 12/23/2013 04:28 PM, Sasha Levin wrote:
> >On 12/23/2013 03:02 PM, Kirill A. Shutemov wrote:
> >>>[ 265.474585] kernel BUG at mm/huge_memory.c:1440!
> >>Could you dump_page() on the bug?
> >
> >[ 469.007946] page:ffffea0005bd8000 count:3 mapcount:0 mapping:ffff8800bcd3d171 index: 0x7fca81000
> >[ 469.009362] page flags: 0x2afffff80090018(uptodate|dirty|swapcache|swapbacked)
>
> Ping? It still shows up in 3.13-rc6.
Sorry, I don't have a theory why it can happen. And I can't reproduce it.
Is there chance to get trinity log after the crash?
--
Kirill A. Shutemov
--
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: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: mm: kernel BUG at mm/huge_memory.c:1440!
Date: Fri, 10 Jan 2014 19:00:16 +0200 [thread overview]
Message-ID: <20140110170016.GA5179@node.dhcp.inet.fi> (raw)
In-Reply-To: <52C819E2.8090509@oracle.com>
On Sat, Jan 04, 2014 at 09:25:38AM -0500, Sasha Levin wrote:
> On 12/23/2013 04:28 PM, Sasha Levin wrote:
> >On 12/23/2013 03:02 PM, Kirill A. Shutemov wrote:
> >>>[ 265.474585] kernel BUG at mm/huge_memory.c:1440!
> >>Could you dump_page() on the bug?
> >
> >[ 469.007946] page:ffffea0005bd8000 count:3 mapcount:0 mapping:ffff8800bcd3d171 index: 0x7fca81000
> >[ 469.009362] page flags: 0x2afffff80090018(uptodate|dirty|swapcache|swapbacked)
>
> Ping? It still shows up in 3.13-rc6.
Sorry, I don't have a theory why it can happen. And I can't reproduce it.
Is there chance to get trinity log after the crash?
--
Kirill A. Shutemov
next prev parent reply other threads:[~2014-01-10 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 19:30 mm: kernel BUG at mm/huge_memory.c:1440! Sasha Levin
2013-12-23 19:30 ` Sasha Levin
2013-12-23 20:02 ` Kirill A. Shutemov
2013-12-23 20:02 ` Kirill A. Shutemov
2013-12-23 20:06 ` Sasha Levin
2013-12-23 20:06 ` Sasha Levin
2013-12-23 21:28 ` Sasha Levin
2013-12-23 21:28 ` Sasha Levin
2014-01-04 14:25 ` Sasha Levin
2014-01-04 14:25 ` Sasha Levin
2014-01-09 10:38 ` Vlastimil Babka
2014-01-09 10:38 ` Vlastimil Babka
2014-01-10 17:00 ` Kirill A. Shutemov [this message]
2014-01-10 17:00 ` Kirill A. Shutemov
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=20140110170016.GA5179@node.dhcp.inet.fi \
--to=kirill@shutemov.name \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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 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.