From: Jake Magee <jakemagee@gmail.com>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: BUG: Bad page map in process
Date: Thu, 3 Dec 2009 14:06:34 -0600 [thread overview]
Message-ID: <a8142e730912031206qe97708av7ef5ccf6fadec397@mail.gmail.com> (raw)
In-Reply-To: <20091203141853.3eafba47@lappy.seanm.ca>
Have you tried the following patches? I'm not sure if they have made
it into the newer releases.
http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg37188.html
Also for reference... http://patchwork.ozlabs.org/patch/34047/
On Thu, Dec 3, 2009 at 1:18 PM, Sean MacLennan <smaclennan@pikatech.com> wr=
ote:
> With 2.6.32 I sometimes get lots and lots of "Bad page map" errors as
> shown below. I believe these started in 2.6.32-rc8 or possibly
> 2.6.32-rc7. Pika just switched to 2.6.31 so I have been concentrating
> on that release, and not really testing the 2.6.32 stream.
>
> I wish I could give more info, but I don't really even have the time to
> write this email :( I am hoping somebody will have a eureka moment.
>
> Cheers,
> =A0 Sean
>
>
> [ =A0147.410448] BUG: Bad page map in process udevd =A0pte:ffffffffffffff=
ff pmd:cd883000
> [ =A0147.417989] addr:48003000 vm_flags:08000875 anon_vma:(null) mapping:=
cf4150ac index:3
> [ =A0147.425837] vma->vm_ops->fault: filemap_fault+0x0/0x410
> [ =A0147.431101] vma->vm_file->f_op->mmap: nfs_file_mmap+0x0/0x94
> [ =A0147.436795] Call Trace:
> [ =A0147.439268] [cf2dbd80] [c00065a4] show_stack+0x48/0x168 (unreliable)
> [ =A0147.445708] [cf2dbdb0] [c0064ac8] print_bad_pte+0x14c/0x204
> [ =A0147.451337] [cf2dbde0] [c0064cd4] vm_normal_page+0x90/0x98
> [ =A0147.456875] [cf2dbdf0] [c0064ee8] unmap_vmas+0x20c/0x638
> [ =A0147.462239] [cf2dbe80] [c0069194] exit_mmap+0xc8/0x170
> [ =A0147.467441] [cf2dbea0] [c001caa4] mmput+0x50/0xf4
> [ =A0147.472195] [cf2dbeb0] [c0020808] exit_mm+0x100/0x138
> [ =A0147.477299] [cf2dbee0] [c00211b0] do_exit+0xb0/0x580
> [ =A0147.482315] [cf2dbf20] [c00216c4] do_group_exit+0x44/0x9c
> [ =A0147.487766] [cf2dbf30] [c0021730] sys_exit_group+0x14/0x28
> [ =A0147.493308] [cf2dbf40] [c000dde4] ret_from_syscall+0x0/0x3c
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2009-12-03 20:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 19:18 BUG: Bad page map in process Sean MacLennan
2009-12-03 20:06 ` Jake Magee [this message]
2009-12-04 0:38 ` Sean MacLennan
2009-12-04 9:08 ` Benjamin Herrenschmidt
2009-12-04 11:00 ` Josh Boyer
2009-12-04 11:18 ` Benjamin Herrenschmidt
2009-12-04 16:37 ` Sean MacLennan
2009-12-08 0:56 ` Sean MacLennan
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=a8142e730912031206qe97708av7ef5ccf6fadec397@mail.gmail.com \
--to=jakemagee@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.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).