From: Andrew Morton <akpm@linux-foundation.org>
To: Xiaotian Feng <xtfeng@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>,
mgorman@suse.de
Subject: Re: kernel BUG at mm/vmscan.c:1114
Date: Tue, 2 Aug 2011 00:22:26 -0700 [thread overview]
Message-ID: <20110802002226.3ff0b342.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAJn8CcG-pNbg88+HLB=tRr26_R+A0RxZEWsJQg4iGe4eY2noXA@mail.gmail.com>
On Tue, 2 Aug 2011 15:09:57 +0800 Xiaotian Feng <xtfeng@gmail.com> wrote:
> __ __I'm hitting the kernel BUG at mm/vmscan.c:1114 twice, each time I
> was trying to build my kernel. The photo of crash screen and my config
> is attached.
hm, now why has that started happening?
Perhaps you could apply this debug patch, see if we can narrow it down?
--- a/mm/vmscan.c~a
+++ a/mm/vmscan.c
@@ -54,6 +54,8 @@
#define CREATE_TRACE_POINTS
#include <trace/events/vmscan.h>
+#define D() do { printk("%s:%d\n", __FILE__, __LINE__); } while (0)
+
/*
* reclaim_mode determines how the inactive list is shrunk
* RECLAIM_MODE_SINGLE: Reclaim only order-0 pages
@@ -1018,27 +1020,37 @@ int __isolate_lru_page(struct page *page
int ret = -EINVAL;
/* Only take pages on the LRU. */
- if (!PageLRU(page))
+ if (!PageLRU(page)) {
+ D();
return ret;
+ }
/*
* When checking the active state, we need to be sure we are
* dealing with comparible boolean values. Take the logical not
* of each.
*/
- if (mode != ISOLATE_BOTH && (!PageActive(page) != !mode))
+ if (mode != ISOLATE_BOTH && (!PageActive(page) != !mode)) {
+ printk("mode:%d\n", mode);
+ D();
return ret;
+ }
- if (mode != ISOLATE_BOTH && page_is_file_cache(page) != file)
+ if (mode != ISOLATE_BOTH && page_is_file_cache(page) != file) {
+ printk("mode: %d, pifc: %d, file: %d\n", mode,
+ page_is_file_cache(page), file);
+ D();
return ret;
-
+ }
/*
* When this function is being called for lumpy reclaim, we
* initially look into all LRU pages, active, inactive and
* unevictable; only give shrink_page_list evictable pages.
*/
- if (PageUnevictable(page))
+ if (PageUnevictable(page)) {
+ D();
return ret;
+ }
ret = -EBUSY;
_
next parent reply other threads:[~2011-08-02 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJn8CcE20-co4xNOD8c+0jMeABrc1mjmGzju3xT34QwHHHFsUA@mail.gmail.com>
[not found] ` <CAJn8CcG-pNbg88+HLB=tRr26_R+A0RxZEWsJQg4iGe4eY2noXA@mail.gmail.com>
2011-08-02 7:22 ` Andrew Morton [this message]
2011-08-03 6:44 ` kernel BUG at mm/vmscan.c:1114 Xiaotian Feng
2011-08-03 8:54 ` Mel Gorman
2011-08-03 9:02 ` Li Zefan
2011-08-04 3:54 ` Xiaotian Feng
2011-08-05 8:42 ` Xiaotian Feng
2011-08-05 9:19 ` Mel Gorman
2011-08-05 12:09 ` Xiaotian Feng
2011-08-05 12:30 ` Xiaotian Feng
2011-08-05 12:55 ` Mel Gorman
2011-08-05 15:51 ` Christoph Lameter
2011-08-02 14:24 ` Mel Gorman
2011-08-02 17:15 ` Andrew Morton
2011-08-03 6:45 ` Xiaotian Feng
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=20110802002226.3ff0b342.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=xtfeng@gmail.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