From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-mm@kvack.org, kernel@avr32linux.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.30] Bad page map in process
Date: Sun, 12 Jul 2009 09:57:31 +0200 [thread overview]
Message-ID: <20090712095731.3090ef56@siona> (raw)
In-Reply-To: <Pine.LNX.4.64.0907101900570.27223@sister.anvils>
On Fri, 10 Jul 2009 19:34:06 +0100 (BST)
Hugh Dickins <hugh.dickins@tiscali.co.uk> wrote:
> I've not looked up avr32 pte layout, is 13f26ed4 good or bad?
> I hope avr32 people can tell more about the likely cause.
It looks OK for a user mapping, assuming you have at least 64MB of
SDRAM (the SDRAM starts at 0x10000000) -- all the normal userspace flags
are set and all the kernel-only flags are unset. It's marked as
executable, so it could be that the segfault was caused by the CPU
executing the wrong code.
The virtual address 0x4377f876 is a bit higher than what you normally
see on avr32 systems, but there's not necessarily anything wrong with
it -- userspace goes up to 0x80000000.
Btw, is preempt enabled when you see this?
Haavard
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-07-12 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 11:07 [BUG 2.6.30] Bad page map in process Guennadi Liakhovetski
2009-07-08 11:23 ` Hans-Christian Egtvedt
2009-07-08 12:28 ` Guennadi Liakhovetski
2009-07-10 18:34 ` Hugh Dickins
2009-07-12 7:57 ` Haavard Skinnemoen [this message]
2009-07-12 19:59 ` Guennadi Liakhovetski
[not found] ` <1DC0FF5051B91B4D88A15F21F1A27F417ABDE6@dware1013.doorway.loc>
2009-07-13 11:14 ` SV: " Guennadi Liakhovetski
2009-07-13 11:56 ` Hugh Dickins
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=20090712095731.3090ef56@siona \
--to=haavard.skinnemoen@atmel.com \
--cc=g.liakhovetski@gmx.de \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kernel@avr32linux.org \
--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 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).