mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alon Bar-Lev" <alon.barlev@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: SH4 - Cannot make initramfs work
Date: Sat, 5 Apr 2008 19:21:59 +0300	[thread overview]
Message-ID: <9e0cf0bf0804050921x46dd7c8dg80dc5b6da024426d@mail.gmail.com> (raw)
In-Reply-To: <9e0cf0bf0804020817s2f558479ve9bca8f82981f7bb@mail.gmail.com>

Hello,

Can anyone help with this issue?
Maybe some idea of how to debug this further?

Thanks!

On 4/2/08, Alon Bar-Lev <alon.barlev@gmail.com> wrote:
> Hello,
>
>  I am trying to boot 2.6.24 kernel on SH4 eb using embedded initramfs.
>
>  The kernel boots, but when trying to decompress the initramfs image it
>  fails with "crc error",
>  resulting from lib/inflate.c::gunzip:1250.
>
>  Has anyone got this error? The initramfs image is correct. I also
>  dumped the memory of __initramfs_start->__initramfs_start and verified
>  that it matches the initramfs image on usr/initramfs_data.cpio.gz.
>
>  I then noticed that the kernel code at
>  init/initramfs::unpack_to_rootfs:459 supports handling
>  uncompressed archives. So I compiled a kernel with uncompressed archived.
>
>  I also hooked the init/initramfs::do_name:585 functions, and see that
>  "/init' is passed
>  to sys_open, and sys_open returns with -EOENT (-2).
>
>  How can it be? shouldn't rootfs always be available?
>
>  The same attempt on i586, mipsel is working as expected.
>
>  Any ideas?
>  1. Why decompression working for kernel and not for initramfs (crc error).
>  2. Why files cannot be created on rootfs?
>
>  Thank you,
>
> Alon Bar-Lev.
>

      reply	other threads:[~2008-04-05 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 15:17 Alon Bar-Lev
2008-04-05 16:21 ` Alon Bar-Lev [this message]

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=9e0cf0bf0804050921x46dd7c8dg80dc5b6da024426d@mail.gmail.com \
    --to=alon.barlev@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®