From: Jake Magee <jakemagee@gmail.com>
To: Jonathan Haws <Jonathan.Haws@sdl.usu.edu>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Page map BUG on program exit
Date: Thu, 22 Oct 2009 17:28:47 -0500 [thread overview]
Message-ID: <a8142e730910221528j185a7d51h6caa604b8695ee50@mail.gmail.com> (raw)
In-Reply-To: <BB99A6BA28709744BF22A68E6D7EB51F0330707311@midas.usurf.usu.edu>
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
Here ya go Jonathan,
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).
- Jake Magee
On Thu, Oct 22, 2009 at 3:57 PM, Jonathan Haws <Jonathan.Haws@sdl.usu.edu>wrote:
> All,
>
> I am using a 405EX CPU on a custom board. The layout and hardware is very
> similar to the AMCC Kilauea board. Here is the output of uname -a:
>
> Linux (none) 2.6.30.3-wolverine-dirty #3 PREEMPT Thu Sep 10 11:41:37 MDT
> 2009 ppc unknown
>
> I am getting the following BUG output when my program exits:
>
> BUG: Bad page map in process main pte:980005d7 pmd:0d840400
> addr:48000000 vm_flags:400844fb anon_vma:(null) mapping:cd8454f8
> index:98000
> vma->vm_file->f_op->mmap: fpga_mmap+0x0/0x178 [fpgaDriver]
> Call Trace:
> [cd84dc40] [c0006f0c] show_stack+0x44/0x16c (unreliable)
> [cd84dc80] [c00ba314] print_bad_pte+0x140/0x1d0
> [cd84dcb0] [c00ba3ec] vm_normal_page+0x48/0x50
> [cd84dcc0] [c00bb2ec] unmap_vmas+0x214/0x614
> [cd84dd40] [c00bffe0] exit_mmap+0xd0/0x1b4
> [cd84dd70] [c0031e40] mmput+0x50/0x134
> [cd84dd80] [c0036470] exit_mm+0x114/0x13c
> [cd84ddb0] [c0037d80] do_exit+0xc0/0x68c
> [cd84de00] [c0038390] do_group_exit+0x44/0xd8
> [cd84de10] [c0044468] get_signal_to_deliver+0x1f8/0x430
> [cd84de70] [c0008224] do_signal+0x54/0x29c
> [cd84df40] [c0010d5c] do_user_signal+0x74/0xc4
>
> I have an FPGA on the PCIe bus that I am mapping BAR0 to user space with a
> call to mmap(). The mapping works just fine and I can access all the
> registers in the BAR without a problem. However, on exit this comes up.
>
> A Google search showed tons of people with similar problems in standard
> distributions (Ubuntu primarily), but no resolutions.
>
> Has anyone seen this crop up before and know what the issue is? I include
> any source code, if that is required.
>
> Thanks!
>
> Jonathan
>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
[-- Attachment #2: Type: text/html, Size: 2734 bytes --]
next prev parent reply other threads:[~2009-10-22 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 20:57 Page map BUG on program exit Jonathan Haws
2009-10-22 22:28 ` Jake Magee [this message]
2009-10-23 17:27 ` Jonathan Haws
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=a8142e730910221528j185a7d51h6caa604b8695ee50@mail.gmail.com \
--to=jakemagee@gmail.com \
--cc=Jonathan.Haws@sdl.usu.edu \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox