Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Judson Wilson <judson@powerstandards.com>
To: buildroot@busybox.net
Subject: [Buildroot] Linux throwing "uncompression error" on rootfs.ext2.gz ?
Date: Mon, 02 Jul 2012 17:57:08 -0700	[thread overview]
Message-ID: <4FF24364.7010303@powerstandards.com> (raw)

Curious if anyone has run into an issue where their ext2.gz image causes 
linux boot to say "uncompression error", like this:

...
RAMDISK: gzip image found at block 0
uncompression error
VFS: Mounted root (ext2 filesystem) on device 1:0.
...

I have two patches to my buildroot install, one that causes this, and 
one that doesn't. Both have the same config file.

I can't imagine this to be caused by the contents of the skeleton, 
unless it is a bug in either buildroot (or its zipper), or my Linux 
kernel (ARM). My kernel is 2.6.37.

I can't see any significant changes in the kernel to 
lib/decompress_inflate.c, lib/zlib_deflate, or lib/zlib_inflate since 
our version.

Also of interest, the suspect file passes a 7zip "Test archive".

Thanks for any help or ideas!
-Judson

             reply	other threads:[~2012-07-03  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  0:57 Judson Wilson [this message]
2012-07-03  7:31 ` [Buildroot] Linux throwing "uncompression error" on rootfs.ext2.gz ? Thomas Petazzoni
2012-07-03 17:13   ` Judson Wilson

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=4FF24364.7010303@powerstandards.com \
    --to=judson@powerstandards.com \
    --cc=buildroot@busybox.net \
    /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