All of lore.kernel.org
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: Initrd and 2.6.33 curious behaviour
Date: Sun, 23 May 2010 12:09:25 +0200	[thread overview]
Message-ID: <87hblz2alm.fsf@free.fr> (raw)
In-Reply-To: <20100523090139.GA950@n2100.arm.linux.org.uk> (Russell King's message of "Sun\, 23 May 2010 10\:01\:39 +0100")

Russell King - ARM Linux <linux@arm.linux.org.uk> writes:

> On Sun, May 23, 2010 at 02:23:33AM +0200, Robert Jarzmik wrote:
> The reason that initrd_start is zero at rd_load_ramdisk is that in
> populate_rootfs(), the initrd is written into the ramfs root as a
> /initrd.image file.  Then the original initrd image is freed, resulting
> in both initrd_start and initrd_end being zeroed.
I understand better now.

> Do you have CONFIG_BLK_DEV_RAM enabled?  Try some debugging (using
> pr_err() and booting with 'quiet' so you can see the output) in
> populate_rootfs().
CONFIG_BLK_DEV_RAM is enabled. I'll add some debugging now and will try again.

Thanks for the help.

--
Robert

  reply	other threads:[~2010-05-23 10:09 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 [this message]
2010-05-24 19:22             ` Robert Jarzmik
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=87hblz2alm.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.