From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 33D4BC433FF for ; Wed, 31 Jul 2019 17:30:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EFC7320679 for ; Wed, 31 Jul 2019 17:30:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=duncanthrax.net header.i=@duncanthrax.net header.b="S92TY3iM" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730009AbfGaRaT (ORCPT ); Wed, 31 Jul 2019 13:30:19 -0400 Received: from smtp.duncanthrax.net ([89.31.1.170]:36512 "EHLO smtp.duncanthrax.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729993AbfGaRaT (ORCPT ); Wed, 31 Jul 2019 13:30:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=duncanthrax.net; s=dkim; h=In-Reply-To:Content-Type:MIME-Version:References :Message-ID:Subject:Cc:To:From:Date; bh=YD8++FvId5PM2bJXQRwW8cE4CclRUTzEl6czrbLcYoU=; b=S92TY3iMJGAD3+tdZsR3poomjt MgA88zziTYejxmuNcKwYwXkuGTd8QJpSSBFah9IOKNkdr7qLsDtNdnu/WFVMe1MmbGMs1J+zOm5T9 BNuYdMRDYEWZS7pfv0nRX4v0kzM+wMrPNMfffWdwLB1Hv0Rq8BpYi5E50Bnpd9prAcfA=; Received: from [134.3.44.134] (helo=t470p.stackframe.org) by smtp.eurescom.eu with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1hssQb-0006ex-Ef; Wed, 31 Jul 2019 19:30:17 +0200 Date: Wed, 31 Jul 2019 19:30:16 +0200 From: Sven Schnelle To: James Bottomley Cc: Parisc List Subject: Re: Compressed kernels currently won't boot Message-ID: <20190731173016.GA23520@t470p.stackframe.org> References: <1564591443.3319.30.camel@HansenPartnership.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1564591443.3319.30.camel@HansenPartnership.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-parisc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org Hi, On Wed, Jul 31, 2019 at 09:44:03AM -0700, James Bottomley wrote: > I noticed this trying to test out compressed kernel booting. The > problem is that a compressed kernel is divided into two pieces, one of > which starts at 0x000e0000 and is the bootstrap code which is > uncompressed into 0x00100000 and the rest of which is the real > compressed kernel which is loaded above the end of the current > decompressed size of the entire kernel. palo decompresses the head and > jumps to it and it then decompresses the rest of the kernel into place. > This means that the first part of the compressed image can't be larger > than 0x20000 == 131072 because otherwise it will be loaded into an area > that decompression will alter. > > The problem is that a change was introduced by > > commit 34c201ae49fe9e0bf3b389da5869d810f201c740 > Author: Helge Deller > Date: Mon Oct 15 22:14:01 2018 +0200 Hmm. This is what i've been facing as well. After reading this commit i'm not sure that the patch i've just sent ("parisc: strip debug information when building compressed images") is really wanted. However, it is really a pain to always copy huge lifimages around when booting parisc machines via LAN. Does someone really extract the vmlinux file from a compressed kernel images? Should we keep that? Regards Sven