From: Willy Tarreau <w@1wt.eu>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
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
Subject: Re: LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64 UEFI runtime)
Date: Mon, 22 Aug 2022 13:58:11 +0200 [thread overview]
Message-ID: <20220822115811.GE17080@1wt.eu> (raw)
In-Reply-To: <34793a7b-64e4-f1cb-b84e-5804b4f6fac3@gmx.com>
On Mon, Aug 22, 2022 at 07:43:18PM +0800, Qu Wenruo wrote:
> Tried to compile gcc10 from AUR, which failed to compile.
>
>
> Anyway, thanks to the advice from Willy, I got the pre-built crosstool
> (gcc 7.5) set up, with some small tweaks like disabling
> CONFIG_RANDOMIZE_BASE to workaround the RELOCS failure, it at least
> compiles for v4.14.0.
>
> Although there is still warning from test_gen_len:
>
> Warning: ffffffff818158cc: 0f ff e9 ud0 %ecx,%ebp
> Warning: objdump says 3 bytes, but insn_get_length() says 2
> Warning: arch/x86/tools/test_get_len found difference at
> <cpu_idle_poll>:ffffffff818159b0
Strange, sounds like a binutils issue though I could be wrong.
> And unfortunately v4.14 still fails to boot, even with GCC 7.5, which
> provides an almost perfect (except above wanrings) build.
>
> I also tried to reduce the CPUid, from host-passthru to qemu64, and
> rebuild, no change (same test_get_len wanrings, same boot failure).
>
> No clue at all now, would try older debian in a VM then.
I suggest that instead of switching distros you should rather first
try 4.14.0 to verify if there was a regression affecting your system.
And if so, then a bisect will certainly be welcome. If it still does
not work, then maybe a different distro could help, though I doubt it.
Willy
next prev parent reply other threads:[~2022-08-22 11:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 1:15 LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64 UEFI runtime) Qu Wenruo
2022-08-22 6:25 ` Greg KH
2022-08-22 7:24 ` Qu Wenruo
2022-08-22 7:33 ` Greg KH
2022-08-22 7:49 ` Qu Wenruo
2022-08-22 7:58 ` Greg KH
2022-08-22 8:13 ` Qu Wenruo
2022-08-22 9:00 ` Greg KH
2022-08-22 11:43 ` Qu Wenruo
2022-08-22 11:58 ` Willy Tarreau [this message]
2022-08-22 12:06 ` Qu Wenruo
2022-08-22 8:04 ` Willy Tarreau
2022-08-22 8:19 ` Qu Wenruo
2022-08-22 8:30 ` Willy Tarreau
2022-08-22 11:07 ` Qu Wenruo
2022-08-22 11:42 ` Greg KH
2022-08-22 11:53 ` Willy Tarreau
2022-08-22 11:59 ` Qu Wenruo
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=20220822115811.GE17080@1wt.eu \
--to=w@1wt.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x86_64@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=stable@vger.kernel.org \
/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