similar to: [PATCH] Fix for crash with certain EFIs

> Thank you all. > > It looks like -mno-red-zone flag is already in master branch since > commit 7d70885d, but it seems it is applied to all EFI builds. Finally we are on the same page. > > IIUC, the problem only affects efi64 builds. Have you actually tested efi32 (ia32) builds? > > So here's the modification of my patch to only apply -mno-red-zone >

Thank you very much for this, I have been running into this issue a number of times but could never get a firm grip on it. Especially HP Gen9 proliants seem to suffer from it by sometimes throwing a stack dump very early in the boot. In the past we worked around it by forcing bios boot. After rebuilding it with -mno-red-zone the problem appears to be fixed, at least after a couple of hours of

Hi Ady, Would it work if we removed "ifdef EFI_BUILD" condition and just add -mno-red-zone for all x86_64 builds? If not, do you have any ideas how to pass this flag? This could work, because the patch is adding the -mno-red-zone flag only for x86_64 builds, which are only used in the form of the efi64 target. The efi32 and bios targets are both 32-bit. BTW. I also tried 6.04-pre1 and

> If the -mno-red-zone flag was already applied for all EFI builds (in > the current git master head and in 6.04-pre1), then what exactly makes > the current 6.04-pre1 *pre-built* binaries fail for you? You are right, Ady. I have no way of knowing whether 6.04-pre1 works or not. I've got this bug from a customer who has systems where syslinux fails. Unfortunately I don't have

> Thank you very much for this, I have been running into this issue a number > of times but could never get a firm grip on it. > > Especially HP Gen9 proliants seem to suffer from it by sometimes throwing a > stack dump very early in the boot. In the past we worked around it by > forcing bios boot. > > > > After rebuilding it with -mno-red-zone the problem

Hello syslinux maintainers, I came across the issue of syslinux crashing with some EFIs in the UEFI boot mode. Upon closer investigation it turned out that most object files which go into syslinux efi64 are compiled with the so-called red zone. Some EFIs follow Windows ABI more strictly and cause syslinux to crash due to stack overwrite. Looking at mk/efi.mk there was a previous attempt to fix

> >> Let me double check what the status of 6.04-pre1 is. Maybe this patch > >> is not necessary at all! > > OK, I have verified beyond doubt that 6.04-pre1 (prebuilt from > kernel.org) indeed does fix the issue on the affected systems. > > Again, sorry for the churn! > > Best Regards, > - Chris OK, so, from the user's point of view, the

> Let me double check what the status of 6.04-pre1 is. Maybe this patch > is not necessary at all! Just a reminder: _ 6.04-pre1 can be downloaded from kernel.org, and it includes pre-built binaries, so no "make" anything is needed (and to some degree, not always recommended). _ In many cases, testing with pre-built official binaries is desired, so others can attempt to

>> Let me double check what the status of 6.04-pre1 is. Maybe this patch >> is not necessary at all! OK, I have verified beyond doubt that 6.04-pre1 (prebuilt from kernel.org) indeed does fix the issue on the affected systems. Again, sorry for the churn! Best Regards, - Chris

Thank you all. It looks like -mno-red-zone flag is already in master branch since commit 7d70885d, but it seems it is applied to all EFI builds. IIUC, the problem only affects efi64 builds. So here's the modification of my patch to only apply -mno-red-zone flag to efi64 target. The patch is against master. I verified that it builds correctly in master. Please feel free to accept or reject

Issue Statement: PXE booting from BIOS systems works fine on both 6.03 and 6.04-pre1. New clients only support (u)EFI which results in the inability to load remote kernel or initrd. Tested with both Syslinux 6.03 and 6.04-pre1. So far unable to boot any (u)EFI clients unless both initrd and kernel are on PXE server. Using packet captures I see that the URI request for the remote file on the repo

On Fri, Apr 6, 2018 at 3:28 PM, Nathan.Wittie--- via Syslinux <syslinux at zytor.com> wrote: > Issue Statement: > PXE booting from BIOS systems works fine on both 6.03 and 6.04-pre1. New clients only support (u)EFI which results in the inability to load remote kernel or initrd. Tested with both Syslinux 6.03 and 6.04-pre1. So far unable to boot any (u)EFI clients unless both initrd and

> Thanks for the hints - I have NOT CONFIG_EFI enabled - do I need this actually? > I do not know which variables I need to boot... The kernel APPEND parameters are > sufficient for me... And the relocatable config is set already. > > .. I enabled the EFI kernel config parts - no change... the console prints: > > Booting System... > Loading linux... ok > Loading

hello everybody, apologies if I'm missing something here Just tried to build 6.04-pre1 test version with: make bios installer and found some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got:

On 06.03.2016 16:47, poma wrote: > ... >> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >> -DHEXDATE="0x56dc3c62" \ >> -Di386 \ >> -I/tmp/syslinux-6.04-pre1/core/ \ >> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \

On 07.03.2016 06:45, poma wrote: > On 06.03.2016 18:23, poma wrote: >> On 06.03.2016 16:47, poma wrote: >>> ... >>>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>>> -DHEXDATE="0x56dc3c62" \ >>>> -Di386 \ >>>> -I/tmp/syslinux-6.04-pre1/core/ \ >>>> -l ldlinux.lsr -o ldlinux.o -MP -MD

On Thu, Jun 16, 2016 at 4:53 AM, Jackson, Dan via Syslinux <syslinux at zytor.com> wrote: > Just tested with the latest VirtualBox and that works OK, so it's definitely something specific to ESXi 6.0.0 (it worked previously under 5.x ESXi versions). > > Thanks, > Dan Jackson (Lead ITServices Technician). > > -----Original Message----- > From: Syslinux

Hello, Thank you, for this information. This is, what I need. So I will switch from 6.03 to the last 6.04 pre. Regards Johann > -----Urspr?ngliche Nachricht----- > Von: Syslinux <syslinux-bounces at syslinux.org> Im Auftrag von Ady Ady via > Syslinux > Gesendet: Montag, 15. April 2019 18:53 > An: syslinux at syslinux.org > Betreff: Re: [syslinux] EFI32, EFI64 on one

On 06.03.2016 18:23, poma wrote: > On 06.03.2016 16:47, poma wrote: >> ... >>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>> -DHEXDATE="0x56dc3c62" \ >>> -Di386 \ >>> -I/tmp/syslinux-6.04-pre1/core/ \ >>> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >>>

... > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ > -I/tmp/syslinux-6.04-pre1/core/ \ > -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ >