Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161583AbWHDXkl (ORCPT ); Fri, 4 Aug 2006 19:40:41 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161584AbWHDXkl (ORCPT ); Fri, 4 Aug 2006 19:40:41 -0400 Received: from mx1.redhat.com ([66.187.233.31]:47265 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1161583AbWHDXkk (ORCPT ); Fri, 4 Aug 2006 19:40:40 -0400 Date: Fri, 4 Aug 2006 19:43:27 -0400 From: Don Zickus To: "Eric W. Biederman" Cc: fastboot@osdl.org, Horms , Jan Kratochvil , "H. Peter Anvin" , Magnus Damm , linux-kernel@vger.kernel.org Subject: Re: [Fastboot] [CFT] ELF Relocatable x86 and x86_64 bzImages Message-ID: <20060804234327.GF16231@redhat.com> References: <20060706081520.GB28225@host0.dyn.jankratochvil.net> <20060707133518.GA15810@in.ibm.com> <20060707143519.GB13097@host0.dyn.jankratochvil.net> <20060710233219.GF16215@in.ibm.com> <20060711010815.GB1021@host0.dyn.jankratochvil.net> <20060804210826.GE16231@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1337 Lines: 36 > The length error comes from lib/inflate.c > > I think it would be interesting to look at orig_len and bytes_out. > > My hunch is that I have tripped over a tool chain bug or a weird > alignment issue. I thought so too, but I took vmlinuz images from people (Vivek) who had it boot on their systems but those images still failed on my two machines. > > The error is the uncompressed length does not math the stored length > of the data before from before we compressed it. Now what is > fascinating is that our crc's match (as that check is performed first). > > Something is very slightly off and I don't see what it is. I printed out orig_len -> 5910532 (which matches vmlinux.bin) bytes_out -> 5910531 > > After looking at the state variables I would probably start looking > at the uncompressed data to see if it really was decompressing > properly. If nothing else that is the kind of process that would tend > to spark a clue. I am not familiar with the code, so very few sparks are flying. I'll still dig through though. Thanks for the tips. Cheers, Don - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/