From: Thomas Capricelli <orzel@freehackers.org>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel failing to boot when compressed with bzip2
Date: Wed, 30 Jan 2013 22:15:33 +0100 [thread overview]
Message-ID: <51098D75.70500@freehackers.org> (raw)
In-Reply-To: <1359554289.32505.58@driftwood>
Il 30/01/2013 14:58, Rob Landley ha scritto:
>
> On 01/20/2013 03:55:05 PM, Thomas Capricelli wrote:
>
>> So my guess is that there's something badly broken in the bzip2 kernel
>> decompressing code.. ? There's both a regression between kernel 3.6 and
>> 3.7, and a problem with gcc-4.7.
> Worked For Me. I note that I built with gcc 4.2.1 and binutils 2.17
> (the last GPLv2 releases), and it's for i686
I guess that's the main point : my bug appears on AMD64, not i686, and i
can trigger It with either gcc-4.6 or gcc-4.7. I'm pretty sure it still
works with such an old gcc as 4.2.1.
I use binutils 2.23.1 but i doubt it matters here.
Again, amd64 using vanilla kernel releases (3.x.y)
linux-3.6 with gcc-4.6 : ok
linux-3.6 with gcc-4.7 : fail
linux-3.7 with gcc-4.6 : fail
linux-3.7 with gcc-4.7 : fail
I've had this BUNZIP2 option for very long, so i'm sure it was working
well with previous versions of both gcc and linux kernel.
greetings,
Thomas
--
Thomas Capricelli <orzel@freehackers.org>
http://www.freehackers.org/thomas/
prev parent reply other threads:[~2013-01-30 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 21:55 Kernel failing to boot when compressed with bzip2 Thomas Capricelli
2013-01-30 13:58 ` Rob Landley
2013-01-30 21:15 ` Thomas Capricelli [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=51098D75.70500@freehackers.org \
--to=orzel@freehackers.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.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