From: Greg KH <gregkh@linuxfoundation.org>
To: Ulrich Gemkow <ulrich.gemkow@ikr.uni-stuttgart.de>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev, ardb@kernel.org
Subject: Re: Regression for PXE boot from patch "Remove the 'bugger off' message" in stable 6.6.18
Date: Tue, 4 Mar 2025 18:40:49 +0100 [thread overview]
Message-ID: <2025030429-battalion-lyricism-c62c@gregkh> (raw)
In-Reply-To: <202503041759.32756.ulrich.gemkow@ikr.uni-stuttgart.de>
On Tue, Mar 04, 2025 at 05:59:32PM +0100, Ulrich Gemkow wrote:
> Hallo,
>
> On Tuesday 04 March 2025, Greg KH wrote:
> > On Tue, Mar 04, 2025 at 03:49:35PM +0100, Ulrich Gemkow wrote:
> > > Hello,
> > >
> > > starting with stable kernel 6.6.18 we have problems with PXE booting.
> > > A bisect shows that the following patch is guilty:
> > >
> > > From 768171d7ebbce005210e1cf8456f043304805c15 Mon Sep 17 00:00:00 2001
> > > From: Ard Biesheuvel <ardb@kernel.org>
> > > Date: Tue, 12 Sep 2023 09:00:55 +0000
> > > Subject: x86/boot: Remove the 'bugger off' message
> > >
> > > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > > Signed-off-by: Ingo Molnar <mingo@kernel.org>
> > > Acked-by: H. Peter Anvin (Intel) <hpa@zytor.com>
> > > Link: https://lore.kernel.org/r/20230912090051.4014114-21-ardb@google.com
> > >
> > > With this patch applied PXE starts, requests the kernel and the initrd.
> > > Without showing anything on the console, the boot process stops.
> > > It seems, that the kernel crashes very early.
> > >
> > > With stable kernel 6.6.17 PXE boot works without problems.
> > >
> > > Reverting this single patch (which is part of a larger set of
> > > patches) solved the problem for us, PXE boot is working again.
> > >
> > > We use the packages syslinux-efi and syslinux-common from Debian 12.
> > > The used boot files are /efi64/syslinux.efi and /ldlinux.e64.
> > >
> > > Our config-File (for 6.6.80) is attached.
> > >
> > > Regarding the patch description, we really do not boot with a floppy :-)
> > >
> > > Any help would be greatly appreciated, I have a bit of a bad feeling
> > > about simply reverting a patch at such a deep level in the kernel.
> >
> > Does newer kernels than 6.7.y work properly? What about the latest
> > 6.12.y release?
> >
> > thanks,
> >
> > greg k-h
> >
>
> Thanks for looking into this!
>
> The latest 6.12.y kernel has the same problem, it also needs reverting
> the mentioned patch. I did not test Kernels in between but I am happy
> to do so, when this gives a hint.
>
> Thanks again and best regards
Great, then this is an issue in Linus's tree and should be fixed there
first.
thansk,
greg k-h
next prev parent reply other threads:[~2025-03-04 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 14:49 Regression for PXE boot from patch "Remove the 'bugger off' message" in stable 6.6.18 Ulrich Gemkow
2025-03-04 16:20 ` Greg KH
2025-03-04 16:59 ` Ulrich Gemkow
2025-03-04 17:40 ` Greg KH [this message]
2025-03-06 10:00 ` Ard Biesheuvel
2025-03-06 10:07 ` Ulrich Gemkow
2025-03-06 14:36 ` Ard Biesheuvel
2025-03-06 14:38 ` H. Peter Anvin
2025-03-06 14:44 ` Ard Biesheuvel
2025-03-06 15:23 ` H. Peter Anvin
2025-03-06 16:03 ` Ard Biesheuvel
2025-03-06 16:50 ` Ulrich Gemkow
2025-03-06 17:07 ` Ard Biesheuvel
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=2025030429-battalion-lyricism-c62c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=ulrich.gemkow@ikr.uni-stuttgart.de \
/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