From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: bad pmd
Date: Wed, 1 Dec 2010 20:14:40 +0000 [thread overview]
Message-ID: <20101201201440.GD29347@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4CF6A7F2.80206@sdgsystems.com>
On Wed, Dec 01, 2010 at 02:54:26PM -0500, Aric D. Blumer wrote:
> Hi. I'm using the long-term stable kernel 2.6.32 on a PXA320 platform,
> and I'm seeing errors like the following:
>
> /home/aric/sdg/git/linux/mm/memory.c:144: bad pmd 8040542e.
>
> I have seen these messages on both the 2.6.32.15 and 2.6.32.24 kernels
> (haven't tried others). Can someone tell me what the message means? I
> suspect memory is being clobbered. One interesting thing is that
> whenever that message is printed, the 8040542e is always the same. I
> have not been able to establish any correlation yet with what causes it.
A pmd value of 0x8040542e is a section mapping, which the generic MM
code will not understand.
It is for address 0x80400000, is read/writable from SVC mode, inaccessible
from user mode, domain 1 (which is normally for 'user' memory), and has
a memory type of TEXCB=10111.
As standard mainline doesn't create mappings with TEX=101, and we don't
create mappings with the 'user' domain using sections, the question this
immediately raises is: have you modified this kernel?
next prev parent reply other threads:[~2010-12-01 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 19:54 bad pmd Aric D. Blumer
2010-12-01 20:14 ` Russell King - ARM Linux [this message]
2010-12-02 2:35 ` Aric D. Blumer
2010-12-07 17:26 ` Aric D. Blumer
2010-12-08 14:02 ` Russell King - ARM Linux
2010-12-14 15:08 ` Matt Reimer
2010-12-29 4:51 ` Eric Miao
2010-12-29 16:23 ` Matt Reimer
2011-01-02 23:51 ` Russell King - ARM Linux
2010-12-29 16:18 ` [PATCH] [ARM] pxa: fix page table corruption on resume Matt Reimer
2011-01-03 15:47 ` Eric Miao
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=20101201201440.GD29347@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).