From: Matthew Schumacher <schu@schu.net>
To: linux-kernel@vger.kernel.org
Subject: Possible bug with kernel decompressor.
Date: Tue, 13 Jul 2004 17:47:34 -0800 [thread overview]
Message-ID: <40F490B6.6000106@schu.net> (raw)
List,
I think I found a bug here because I can repeatably get the same kernel
(checked with md5sum) to decompress and to fail with the error:
invalid compressed format (err=2)
--System halted
Here is how I can reproduce the problem:
Boot 2.6.8-rc1
Run md5sum on 2.6.8-rc1 kernel
Turn power off (this is an embedded system with only ramdisk mounted)
Turn power on
Kernel fails to boot with "invalid compressed format (err=2)"
Restart system
Boot 2.4.26
Run md5sum on 2.6.8-rc1 kernel (matches md5sum above)
Shutdown properly
boot 2.6.8-rc1 (works fine)
Run md5sum on 2.6.8-rc1 kernel (matches md5sum above)
So you see if I don't shutdown properly (which shouldn't be required for
an embedded system using a ramdisk) my kernel won't decompress itself
until I run another kernel and shutdown properly. I know that the
kernel didn't change so something else must be causing it to fail.
I call this a bug simply because a power failure could cause someone to
loose the ability to boot their machine.
Here is the hardware:
Whistle Interjet (486 SBC)
64MB of memory
IDE disk.
Can reproduce with linux 2.6.5, 2.6.6, 2.6.7, and 2.6.8-rc1
Both kernel images and the initrd image both live on a fat16 partition
and are started with syslinux. I can reproduce this problem with any
version of syslinux I have tried.
Please CC me in any replies since I am not on the list.
Thanks,
schu
next reply other threads:[~2004-07-14 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 1:47 Matthew Schumacher [this message]
[not found] ` <40F5AE63.5010505@am.sony.com>
2004-07-15 17:55 ` Possible bug with kernel decompressor Matthew Schumacher
2004-07-15 19:39 ` [syslinux] " H. Peter Anvin
2004-07-15 20:40 ` Matthew Schumacher
2004-07-15 20:58 ` H. Peter Anvin
2004-07-16 15:57 ` Meelis Roos
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=40F490B6.6000106@schu.net \
--to=schu@schu.net \
--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 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.