From: robert.jarzmik@free•fr (Robert Jarzmik)
To: linux-arm-kernel@lists•infradead.org
Subject: Initrd and 2.6.33 curious behaviour
Date: Mon, 24 May 2010 21:22:17 +0200 [thread overview]
Message-ID: <87r5l114wm.fsf@free.fr> (raw)
In-Reply-To: <87hblz2alm.fsf@free.fr> (Robert Jarzmik's message of "Sun\, 23 May 2010 12\:09\:25 +0200")
Robert Jarzmik <robert.jarzmik@free•fr> writes:
> CONFIG_BLK_DEV_RAM is enabled. I'll add some debugging now and will try again.
>
OK, found out the culprit.
My bootloader(haret) is to be blamed : the first 6 bytes of initrd as the kernel
sees them are totally different from the actual 6 first bytes of initrd file.
The long story is that when haret stops wince MMU, it "reorders" the pages to
create a physically contiguous kernel and initrd, from the scattered pages
allocated in wince. The relocation algorithm is faulty, as it doesn't cope with
the cases where there is a double dependency (ie. a kernel page should be moved
to the page occupied by a initrd page, and the initrd page should be moved to
where resides the kernel page).
It's funny how people want to solve the hanoi towers problem without a spare
slot ...
Cheers.
--
Robert
next prev parent reply other threads:[~2010-05-24 19:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 20:27 Initrd and 2.6.33 curious behaviour Robert Jarzmik
2010-05-21 20:43 ` Russell King - ARM Linux
2010-05-22 9:36 ` Robert Jarzmik
2010-05-22 9:37 ` Robert Jarzmik
2010-05-22 9:46 ` Russell King - ARM Linux
2010-05-23 0:23 ` Robert Jarzmik
2010-05-23 9:01 ` Russell King - ARM Linux
2010-05-23 10:09 ` Robert Jarzmik
2010-05-24 19:22 ` Robert Jarzmik [this message]
2010-05-27 12:00 ` Robert Jarzmik
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=87r5l114wm.fsf@free.fr \
--to=robert.jarzmik@free$(echo .)fr \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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