From: Jared Hulbert <jaredeh@gmail.com>
To: Nicolas Pitre <nico@cam.org>
Cc: "Korolev, Alexey" <alexey.korolev@intel.com>,
linux-mtd@lists.infradead.org
Subject: Re: XIP fails on kernels 2.6.12 and higher
Date: Thu, 29 Sep 2005 15:51:50 -0700 [thread overview]
Message-ID: <6934efce05092915519ffe76c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0509221318180.18381@localhost.localdomain>
> If you can find the exact intermediate release between 2.6.11 and 2.6.12
> that broke it that would be extrelely helpful.
2.6.11.12 works and 2.6.12 does not. I'll see if I can't find an
intermediate release.
> This is generic code so probably on all platforms.
In mm/bootmem.c free_all_bootmem_core() does not return. It seems
after i hits 288 if I step I get a imprecise data abort. It seems to
occur at the __ClearPageReserved() which is an inlined __clear_bit()
from include/asm/bitops.h. It does this at somewhere around
page=0xC0042400 which seems perfectly normal and is readable/writeable
with the JTAG debugger. Its really hard to replicate but it seems
like a LDR op code is always at fault. I've tried 2 different
toolchains and compiling with -O0, while the LDR command was always a
little different it was basically a read to the same address range.
It is really baffling me. Nothing seems wrong with what it is doing.
I almost suspect hardware. I'm also testing on a Mainstone2 like
Alexey. My OSK got destroyed. Can somebody confirm xipImage of
2.6.12 fails to boot where 2.6.11 runs on a different hardware
platform?
next prev parent reply other threads:[~2005-09-29 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 16:08 XIP fails on kernels 2.6.12 and higher Korolev, Alexey
2005-09-22 17:20 ` Nicolas Pitre
2005-09-29 22:51 ` Jared Hulbert [this message]
2005-10-05 11:42 ` Konstantin Kletschke
2005-10-12 19:05 ` Jared Hulbert
2005-10-12 20:23 ` Nicolas Pitre
2005-10-12 20:49 ` Konstantin Kletschke
2005-10-12 21:22 ` Jared Hulbert
2005-10-05 11:45 ` Konstantin Kletschke
2005-10-06 13:31 ` Konstantin Kletschke
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=6934efce05092915519ffe76c@mail.gmail.com \
--to=jaredeh@gmail.com \
--cc=alexey.korolev@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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