Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <a002f2a6-7c5f-c8f1-f331-7f1ca47132f9@gmx.com>
Date:   Mon, 22 Aug 2022 19:59:14 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.12.0
Subject: Re: LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64
 UEFI runtime)
Content-Language: en-US
To:     Willy Tarreau <w@1wt.eu>
Cc:     Greg KH <gregkh@linuxfoundation.org>,
        stable <stable@vger.kernel.org>,
        "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-x86_64@vger.kernel.org
References: <2d6012e8-805d-4225-80ed-d317c28f1899@gmx.com>
 <YwMhXX6OhROLZ/LR@kroah.com> <1ed5a33a-b667-0e8e-e010-b4365f3713d6@gmx.com>
 <YwMxRAfrrsPE6sNI@kroah.com> <8aff5c17-d414-2412-7269-c9d15f574037@gmx.com>
 <20220822080456.GB17080@1wt.eu>
 <4c42af33-dc05-315a-87d9-be0747a74df4@gmx.com>
 <20220822083044.GC17080@1wt.eu>
 <9aa83875-0a05-6b28-b4df-4071ba8ee343@gmx.com>
 <20220822115326.GD17080@1wt.eu>
From:   Qu Wenruo <quwenruo.btrfs@gmx.com>
In-Reply-To: <20220822115326.GD17080@1wt.eu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Precedence: bulk


On 2022/8/22 19:53, Willy Tarreau wrote:
> On Mon, Aug 22, 2022 at 07:07:19PM +0800, Qu Wenruo wrote:
>>
>>
>> On 2022/8/22 16:30, Willy Tarreau wrote:
>>> On Mon, Aug 22, 2022 at 04:19:49PM +0800, Qu Wenruo wrote:
>>>>> Regardless, if you need an older compiler, just use these ones:
>>>>>
>>>>>       https://mirrors.edge.kernel.org/pub/tools/crosstool/
>>>>>
>>>>> They go back to 4.9.4 for x86, you'll surely find the right one for =
your
>>>>> usage. I've long used 4.7.4 for kernels up to 4.9 and 6.5 for 4.19 a=
nd
>>>>> above, so something within that area will surely match your needs.
>>>>
>>>> BTW, it would be way more awesome if the page can provide some hint o=
n
>>>> the initial release date of the compilers.
>>>>
>>>> It would help a lot of choose the toolchain then.
>>>
>>> It wouldn't help, if you look closely, you'll notice that in the "othe=
r
>>> releases" section you have the most recent version of each of them. Th=
at
>>> does not preclude the existence of the branch earlier. For example gcc=
-9
>>> was released in 2019 and 9.5 was emitted 3 years later. That's quite a=
n
>>> amplitude that doesn't help.
>>
>> Maybe I'm totally wrong, but if GCC10.1 is released May 2020, and even
>> 10.4 is released 2022, then shouldn't we expect the kernel releases
>> around 2020 can be compiled for all GCC 10.x releases?
>>
>> Thus the initial release date should be a good enough hint for most cas=
es.
>
> If you speak about initial release, yes that should generally be a valid
> assumption.
>
>> If go this method, for v4.14 I guess I should go gcc 7.x, as gcc 7.1 is
>> released May 2017, even the latest 7.5 is released 2019.
>
> Then it should definitely work. But I think you're spending way too much
> time comparing dates and discussing on the subject. By the time it took
> to check these dates, you could already have downloaded one such compile=
r
> and built a kernel to verify it did build correctly ;-)

That's completely true.

Except the fact that, even with time period correct tool chain (gcc
7.5), the compiled v4.14.x kernel (tried both 4.14.0 and latest
4.14.290), neither can boot nor cause any early boot message to pop up. :(

Anyway, thank you very much for the toolchain part, it would definitely
help for my future adventure related to stable kernels (looking at tons
of v4.12 related branches with sad face).

Thanks,
Qu

>
> Willy