Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: stable <stable@vger.kernel.org>
Cc: "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: LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64 UEFI runtime)
Date: Mon, 22 Aug 2022 09:15:59 +0800	[thread overview]
Message-ID: <2d6012e8-805d-4225-80ed-d317c28f1899@gmx.com> (raw)

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?

Thanks,
Qu

             reply	other threads:[~2022-08-22  1:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  1:15 Qu Wenruo [this message]
2022-08-22  6:25 ` LTS kernel Linux 4.14.290 unable to boot with edk2-ovmf (x86_64 UEFI runtime) 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
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=2d6012e8-805d-4225-80ed-d317c28f1899@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-x86_64@vger.kernel.org \
    --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