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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id CB25FC28D13 for ; Mon, 22 Aug 2022 07:58:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233481AbiHVH6U (ORCPT ); Mon, 22 Aug 2022 03:58:20 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50510 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229882AbiHVH6T (ORCPT ); Mon, 22 Aug 2022 03:58:19 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C01CE1BA; Mon, 22 Aug 2022 00:58:12 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 830E7B80E9E; Mon, 22 Aug 2022 07:58:11 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C511FC433D6; Mon, 22 Aug 2022 07:58:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1661155090; bh=oj7YS48yYvRZgeoU3nxjZEqvfr+ShGiRpCR6wm3JQCU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=jJlMWhiK+/vEhIinEYOaB2nPlQ+58o9wKMFI8gHsJQ37q8VpNmZCFNjfAQ678KT1U eJ2XOHpYZc+xv7cxUTOBlBTcZtcNW7+almtJS30xLmTjllSjQgbX5mus3lkapiZTw5 KkIIo0PTutgsfJng1/uCBDR5faxv3B/Iov/BIar4= Date: Mon, 22 Aug 2022 09:58:07 +0200 From: Greg KH To: Qu Wenruo Cc: stable , "linux-btrfs@vger.kernel.org" , Linux Kernel Mailing List , linux-x86_64@vger.kernel.org Subject: Re: LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64 UEFI runtime) Message-ID: References: <2d6012e8-805d-4225-80ed-d317c28f1899@gmx.com> <1ed5a33a-b667-0e8e-e010-b4365f3713d6@gmx.com> <8aff5c17-d414-2412-7269-c9d15f574037@gmx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8aff5c17-d414-2412-7269-c9d15f574037@gmx.com> Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Mon, Aug 22, 2022 at 03:49:51PM +0800, Qu Wenruo wrote: > > > On 2022/8/22 15:33, Greg KH wrote: > > On Mon, Aug 22, 2022 at 03:24:53PM +0800, Qu Wenruo wrote: > > > > > > > > > On 2022/8/22 14:25, Greg KH wrote: > > > > On Mon, Aug 22, 2022 at 09:15:59AM +0800, Qu Wenruo wrote: > > > > > Hi, > > > > > > > > > > When backporting some btrfs specific patches to all LTS kernels, I found > > > > > v4.14.290 kernel unable to boot as a KVM guest with edk2-ovmf > > > > > (edk2-ovmf: 202205, qemu 7.0.0, libvirt 1:8.6.0). > > > > > > > > > > While all other LTS/stable branches (4.19.x, 5.4.x, 5.10.x, 5.15.x, > > > > > 5.18.x, 5.19.x) can boot without a hipccup. > > > > > > > > > > I tried the following configs, but none of them can even provide an > > > > > early output: > > > > > > > > > > - CONFIG_X86_VERBOSE_BOOTUP > > > > > - CONFIG_EARLY_PRINTK > > > > > - CONFIG_EARLY_PRINTK_EFI > > > > > > > > > > Is this a known bug or something new? > > > > > > > > Has this ever worked properly on this very old kernel tree? If so, can > > > > you use 'git bisect' to find the offending commit? > > > > > > Unfortunately the initial v4.14 from upstream can not even be compiled. > > > > Really? Try using an older version of gcc and you should be fine. It > > did build properly back in 2017 when it was released :) > > Yeah, I'm pretty sure my toolchain is too new for v4.14.0. But my distro > only provides the latest and mostly upstream packages. > > It may be a even worse disaster to find a way to rollback to older > toolchains using my distro... > > Also my hardware may not be well suited for older kernels either. > (Zen 3 CPU used here) > > In fact, I even find it hard just to locate a v4.14.x tag that can compile. > After some bisection between v4.14.x tags, only v4.14.268 and newer tags > can even be compiled using latest toolchain. > (But still tons of warning, and tons of objdump warnings against > insn_get_length()). > > I'm not sure what's the normal practice for backports to such old branch. > > Do you stable guys keep dedicated VMs loaded with older distro just for > these old branches? I don't, that's why those kernels can be built with newer versions of gcc. Your distro should have a version of gcc-10 or gcc-9 that can be installed, right? Or maybe use the gcc versions on kernel.org that only work for kernel builds? > If so, any recommendation on those kinda retro distro? Try installing an old version of Debian, or better yet, use a distro that provides old versions of gcc :) good luck! greg k-h