From: Jake Magee <jakemagee@gmail.com>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: BUG: Bad page map in process mm2
Date: Mon, 8 Mar 2010 19:26:16 -0600 [thread overview]
Message-ID: <a8142e731003081726j1b60e9dfyeead2e89bc51a5e5@mail.gmail.com> (raw)
In-Reply-To: <4B956CD9.9090401@harris.com>
[-- Attachment #1: Type: text/plain, Size: 2916 bytes --]
Steven,
Try these patches...
http://patchwork.ozlabs.org/patch/34047/
http://patchwork.ozlabs.org/patch/34113/
Both patches work for my situation, but I went with the second set as a
final patch(34113).
On Mon, Mar 8, 2010 at 3:32 PM, Steven A. Falco <sfalco@harris.com> wrote:
> Steven A. Falco wrote:
>
> Apologies - previous crash dump was mangled by the
> interspersed program output. Here is one showing
> just the crash dump.
>
> Interestingly, the program does produce correct output,
> as verified by dd'ing from /dev/mem to a file, then
> doing "od" on the result. So in some sense, the error
> is spurious.
>
> Steve
>
> # ./mm2 > foo 2>&1
> BUG: Bad page map in process mm2 pte:00000452 pmd:0f6c8400
> page:c0396000 flags:00000404 count:1 mapcount:-1 mapping:(null) index:0
> addr:4801f000 vm_flags:400844fb anon_vma:(null) mapping:cea78430 index:0
> vma->vm_ops->fault: 0x0
> vma->vm_file->f_op->mmap: mmap_mem+0x0/0xa4
> Call Trace:
> [cf4c5d90] [c0006cf4] show_stack+0x44/0x16c (unreliable)
> [cf4c5dd0] [c0067800] print_bad_pte+0x140/0x1cc
> [cf4c5e00] [c0068640] unmap_vmas+0x41c/0x594
> [cf4c5e80] [c006c8f0] exit_mmap+0xb8/0x150
> [cf4c5ea0] [c0020948] mmput+0x50/0xe0
> [cf4c5eb0] [c0024504] exit_mm+0xec/0x10c
> [cf4c5ee0] [c0025bd0] do_exit+0xc4/0x5d4
> [cf4c5f20] [c0026124] do_group_exit+0x44/0xa4
> [cf4c5f30] [c0026198] sys_exit_group+0x14/0x28
> [cf4c5f40] [c000edcc] ret_from_syscall+0x0/0x3c
> Disabling lock debugging due to kernel taint
> BUG: Bad page state in process mm2 pfn:00000
> page:c0396000 flags:00000404 count:0 mapcount:-1 mapping:(null) index:0
> Call Trace:
> [cf4c5d80] [c0006cf4] show_stack+0x44/0x16c (unreliable)
> [cf4c5dc0] [c00585bc] bad_page+0x94/0x12c
> [cf4c5de0] [c005d234] put_page+0x4c/0x170
> [cf4c5df0] [c0073e54] free_page_and_swap_cache+0x34/0x8c
> [cf4c5e00] [c0068490] unmap_vmas+0x26c/0x594
> [cf4c5e80] [c006c8f0] exit_mmap+0xb8/0x150
> [cf4c5ea0] [c0020948] mmput+0x50/0xe0
> [cf4c5eb0] [c0024504] exit_mm+0xec/0x10c
> [cf4c5ee0] [c0025bd0] do_exit+0xc4/0x5d4
> [cf4c5f20] [c0026124] do_group_exit+0x44/0xa4
> [cf4c5f30] [c0026198] sys_exit_group+0x14/0x28
> [cf4c5f40] [c000edcc] ret_from_syscall+0x0/0x3c
> # cat foo
> 00000000: 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378
> 00000010: 7cfb3b78 480022ad 3c000002 60001032
> 00000020: 7c1b03a6 3c00c000 60002210 7c1a03a6
> 00000030: 4c000064 48000000 00000000 00000000
> # dd count=1 if=/dev/mem of=goo
> # od -X goo
> 0000000 7c7f1b78 7c9e2378 7cbd2b78 7cdc3378
> 0000020 7cfb3b78 480022ad 3c000002 60001032
> 0000040 7c1b03a6 3c00c000 60002210 7c1a03a6
> 0000060 4c000064 48000000 00000000 00000000
> 0000100
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
[-- Attachment #2: Type: text/html, Size: 3796 bytes --]
next prev parent reply other threads:[~2010-03-09 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 20:43 BUG: Bad page map in process mm2 Steven A. Falco
2010-03-08 21:32 ` Steven A. Falco
2010-03-09 1:26 ` Jake Magee [this message]
2010-03-09 14:48 ` Steven A. Falco
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=a8142e731003081726j1b60e9dfyeead2e89bc51a5e5@mail.gmail.com \
--to=jakemagee@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfalco@harris.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).