From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.11-rc4: OMAP1/Amstrad Delta (E3) crash
Date: Thu, 8 Aug 2013 12:01:08 +0100 [thread overview]
Message-ID: <20130808110108.GK23053@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130806232609.GB15014@blackmetal.musicnaut.iki.fi>
On Wed, Aug 07, 2013 at 02:26:09AM +0300, Aaro Koskinen wrote:
> [ 0.258589] [ffff1224] *pgd=00000000, *pte=11fff0cb000001f1, *ppte=11fff00a00000000
BTW, your oops dump is interesting for another reason - the above.
You seem to have 64-bit page table entries above. This is produced
by this:
pte_t *pte;
...
printk(", *pte=%08llx", (long long)pte_val(*pte));
#ifndef CONFIG_ARM_LPAE
printk(", *ppte=%08llx",
(long long)pte_val(pte[PTE_HWTABLE_PTRS]));
#endif
with:
#define pte_val(x) (x)
typedef pteval_t pte_t;
typedef u32 pteval_t;
Now, this is totally legal C:
unsigned int val = 0x12345678;
printk("%08llx\n", (long long)val);
and it should produce "12345678" but I'm willing to bet with your compiler
it produces "12345678xxxxxxxx" where xxxxxxxx is just what happens to be
sitting in some register. IOW, I think you have a compiler bug here. Can
you investigate what's going on with this yourself please?
next prev parent reply other threads:[~2013-08-08 11:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 23:26 v3.11-rc4: OMAP1/Amstrad Delta (E3) crash Aaro Koskinen
2013-08-07 19:05 ` Aaro Koskinen
2013-08-07 23:08 ` Russell King - ARM Linux
2013-08-08 0:05 ` Aaro Koskinen
2013-08-08 11:02 ` Russell King - ARM Linux
2013-08-08 11:01 ` Russell King - ARM Linux [this message]
2013-08-08 21:11 ` Aaro Koskinen
2013-08-08 22:28 ` Aaro Koskinen
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=20130808110108.GK23053@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