From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: BUG: Bad page state in process (current git)
Date: Wed, 10 Nov 2010 16:25:19 +0100 [thread overview]
Message-ID: <20101110152519.GA1626@arch.trippelsdorf.de> (raw)
This happend twice in the last 24h on my machine:
Nov 9 20:29:42 arch kernel: BUG: Bad page state in process mutt pfn:a6869
Nov 9 20:29:42 arch kernel: page:ffffea000246d6f8 count:0 mapcount:0 mapping: (null) index:0x0
Nov 9 20:29:42 arch kernel: page flags: 0x4000000000000008(uptodate)
Nov 9 20:29:42 arch kernel: Pid: 1794, comm: mutt Not tainted 2.6.37-rc1-00168-gb369291-dirty #72
Nov 9 20:29:42 arch kernel: Call Trace:
Nov 9 20:29:42 arch kernel: [<ffffffff810a1d32>] ? bad_page+0x92/0xe0
Nov 9 20:29:42 arch kernel: [<ffffffff810a2f50>] ? get_page_from_freelist+0x4b0/0x570
Nov 9 20:29:42 arch kernel: [<ffffffff810a3123>] ? __alloc_pages_nodemask+0x113/0x6b0
Nov 9 20:29:42 arch kernel: [<ffffffff8109c5f4>] ? find_get_page+0x64/0xb0
Nov 9 20:29:42 arch kernel: [<ffffffff8109c858>] ? filemap_fault+0x98/0x4b0
Nov 9 20:29:42 arch kernel: [<ffffffff811807ec>] ? cpumask_any_but+0x2c/0x40
Nov 9 20:29:42 arch kernel: [<ffffffff810b4acc>] ? do_wp_page+0xbc/0x7e0
Nov 9 20:29:42 arch kernel: [<ffffffff810b6ab3>] ? handle_mm_fault+0x4e3/0x970
Nov 9 20:29:42 arch kernel: [<ffffffff8104b1d0>] ? do_page_fault+0x120/0x410
Nov 9 20:29:42 arch kernel: [<ffffffff8144af8f>] ? page_fault+0x1f/0x30
Nov 9 20:29:42 arch kernel: [<ffffffff8118a09d>] ? __put_user_4+0x1d/0x30
Nov 9 20:29:42 arch kernel: [<ffffffff8144af8f>] ? page_fault+0x1f/0x30
Nov 9 20:29:42 arch kernel: Disabling lock debugging due to kernel taint
Nov 10 14:35:25 arch kernel: BUG: Bad page state in process firefox-bin pfn:a049d
Nov 10 14:35:25 arch kernel: page:ffffea0002310258 count:0 mapcount:0 mapping: (null) index:0x0
Nov 10 14:35:25 arch kernel: page flags: 0x4000000000000008(uptodate)
Nov 10 14:35:25 arch kernel: Pid: 23080, comm: firefox-bin Not tainted 2.6.37-rc1-00168-gb369291-dirty #72
Nov 10 14:35:25 arch kernel: Call Trace:
Nov 10 14:35:25 arch kernel: [<ffffffff810a1d32>] ? bad_page+0x92/0xe0
Nov 10 14:35:25 arch kernel: [<ffffffff810a2f50>] ? get_page_from_freelist+0x4b0/0x570
Nov 10 14:35:25 arch kernel: [<ffffffff8105325c>] ? enqueue_task_fair+0x14c/0x190
Nov 10 14:35:25 arch kernel: [<ffffffff810a3123>] ? __alloc_pages_nodemask+0x113/0x6b0
Nov 10 14:35:25 arch kernel: [<ffffffff8109bb04>] ? file_read_actor+0xc4/0x190
Nov 10 14:35:25 arch kernel: [<ffffffff8109d788>] ? generic_file_aio_read+0x558/0x6a0
Nov 10 14:35:25 arch kernel: [<ffffffff810b6c8d>] ? handle_mm_fault+0x6bd/0x970
Nov 10 14:35:25 arch kernel: [<ffffffff810cda2f>] ? do_sync_read+0xbf/0x100
Nov 10 14:35:25 arch kernel: [<ffffffff8104b1d0>] ? do_page_fault+0x120/0x410
Nov 10 14:35:25 arch kernel: [<ffffffff810bbf7f>] ? mmap_region+0x1df/0x4b0
Nov 10 14:35:25 arch kernel: [<ffffffff81448295>] ? schedule+0x285/0x850
Nov 10 14:35:25 arch kernel: [<ffffffff8144af8f>] ? page_fault+0x1f/0x30
Nov 10 14:35:25 arch kernel: Disabling lock debugging due to kernel taint
My memory is fine as far as I can tell (memtest and a linpack stress
test ran without errors).
Any ideas on what might be going on?
(The dirty flag is due to this patch: https://patchwork.kernel.org/patch/311202/)
--
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
Subject: BUG: Bad page state in process (current git)
Date: Wed, 10 Nov 2010 16:25:19 +0100 [thread overview]
Message-ID: <20101110152519.GA1626@arch.trippelsdorf.de> (raw)
This happend twice in the last 24h on my machine:
Nov 9 20:29:42 arch kernel: BUG: Bad page state in process mutt pfn:a6869
Nov 9 20:29:42 arch kernel: page:ffffea000246d6f8 count:0 mapcount:0 mapping: (null) index:0x0
Nov 9 20:29:42 arch kernel: page flags: 0x4000000000000008(uptodate)
Nov 9 20:29:42 arch kernel: Pid: 1794, comm: mutt Not tainted 2.6.37-rc1-00168-gb369291-dirty #72
Nov 9 20:29:42 arch kernel: Call Trace:
Nov 9 20:29:42 arch kernel: [<ffffffff810a1d32>] ? bad_page+0x92/0xe0
Nov 9 20:29:42 arch kernel: [<ffffffff810a2f50>] ? get_page_from_freelist+0x4b0/0x570
Nov 9 20:29:42 arch kernel: [<ffffffff810a3123>] ? __alloc_pages_nodemask+0x113/0x6b0
Nov 9 20:29:42 arch kernel: [<ffffffff8109c5f4>] ? find_get_page+0x64/0xb0
Nov 9 20:29:42 arch kernel: [<ffffffff8109c858>] ? filemap_fault+0x98/0x4b0
Nov 9 20:29:42 arch kernel: [<ffffffff811807ec>] ? cpumask_any_but+0x2c/0x40
Nov 9 20:29:42 arch kernel: [<ffffffff810b4acc>] ? do_wp_page+0xbc/0x7e0
Nov 9 20:29:42 arch kernel: [<ffffffff810b6ab3>] ? handle_mm_fault+0x4e3/0x970
Nov 9 20:29:42 arch kernel: [<ffffffff8104b1d0>] ? do_page_fault+0x120/0x410
Nov 9 20:29:42 arch kernel: [<ffffffff8144af8f>] ? page_fault+0x1f/0x30
Nov 9 20:29:42 arch kernel: [<ffffffff8118a09d>] ? __put_user_4+0x1d/0x30
Nov 9 20:29:42 arch kernel: [<ffffffff8144af8f>] ? page_fault+0x1f/0x30
Nov 9 20:29:42 arch kernel: Disabling lock debugging due to kernel taint
Nov 10 14:35:25 arch kernel: BUG: Bad page state in process firefox-bin pfn:a049d
Nov 10 14:35:25 arch kernel: page:ffffea0002310258 count:0 mapcount:0 mapping: (null) index:0x0
Nov 10 14:35:25 arch kernel: page flags: 0x4000000000000008(uptodate)
Nov 10 14:35:25 arch kernel: Pid: 23080, comm: firefox-bin Not tainted 2.6.37-rc1-00168-gb369291-dirty #72
Nov 10 14:35:25 arch kernel: Call Trace:
Nov 10 14:35:25 arch kernel: [<ffffffff810a1d32>] ? bad_page+0x92/0xe0
Nov 10 14:35:25 arch kernel: [<ffffffff810a2f50>] ? get_page_from_freelist+0x4b0/0x570
Nov 10 14:35:25 arch kernel: [<ffffffff8105325c>] ? enqueue_task_fair+0x14c/0x190
Nov 10 14:35:25 arch kernel: [<ffffffff810a3123>] ? __alloc_pages_nodemask+0x113/0x6b0
Nov 10 14:35:25 arch kernel: [<ffffffff8109bb04>] ? file_read_actor+0xc4/0x190
Nov 10 14:35:25 arch kernel: [<ffffffff8109d788>] ? generic_file_aio_read+0x558/0x6a0
Nov 10 14:35:25 arch kernel: [<ffffffff810b6c8d>] ? handle_mm_fault+0x6bd/0x970
Nov 10 14:35:25 arch kernel: [<ffffffff810cda2f>] ? do_sync_read+0xbf/0x100
Nov 10 14:35:25 arch kernel: [<ffffffff8104b1d0>] ? do_page_fault+0x120/0x410
Nov 10 14:35:25 arch kernel: [<ffffffff810bbf7f>] ? mmap_region+0x1df/0x4b0
Nov 10 14:35:25 arch kernel: [<ffffffff81448295>] ? schedule+0x285/0x850
Nov 10 14:35:25 arch kernel: [<ffffffff8144af8f>] ? page_fault+0x1f/0x30
Nov 10 14:35:25 arch kernel: Disabling lock debugging due to kernel taint
My memory is fine as far as I can tell (memtest and a linpack stress
test ran without errors).
Any ideas on what might be going on?
(The dirty flag is due to this patch: https://patchwork.kernel.org/patch/311202/)
--
Markus
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2010-11-10 15:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 15:25 Markus Trippelsdorf [this message]
2010-11-10 15:25 ` BUG: Bad page state in process (current git) Markus Trippelsdorf
2010-11-10 15:40 ` Markus Trippelsdorf
2010-11-10 15:40 ` Markus Trippelsdorf
2010-11-10 21:46 ` Christoph Lameter
2010-11-10 21:46 ` Christoph Lameter
2010-11-12 12:20 ` Markus Trippelsdorf
2010-11-12 12:20 ` Markus Trippelsdorf
2010-11-15 12:38 ` Markus Trippelsdorf
2010-11-15 12:38 ` Markus Trippelsdorf
2010-11-15 19:54 ` Markus Trippelsdorf
2010-11-15 19:54 ` Markus Trippelsdorf
2010-11-15 21:23 ` Hugh Dickins
2010-11-15 21:23 ` Hugh Dickins
2010-11-15 21:23 ` Hugh Dickins
2010-11-16 11:13 ` [PATCH] ext4 Fix setting random pages PageUptodate Markus Trippelsdorf
2010-11-16 11:13 ` Markus Trippelsdorf
2010-11-16 11:13 ` Markus Trippelsdorf
2010-11-16 20:38 ` Ted Ts'o
2010-11-16 20:38 ` Ted Ts'o
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=20101110152519.GA1626@arch.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.