Syslinux - Jun 2019 - lpxelinux.0 issues with larger initrd.img files from RHEL >= 7.5 on UCS servers?

On Wed, May 22, 2019 at 03:18:25PM +0000, Ady Ady via Syslinux
wrote:
> You also need (at least) the "syslinux-common" package of the
same
> version
Yeah my bad, that's what I used, I had all the c32 files...
> I don't know how much relevant debug info you could actually get when 
> using the "-dhcpinfo" option of linux.c32 (see the wiki for
details).
I'll give it a shot nonetheless...
> Probably what is needed here is someone with the relevant knowledge and 
> experience in this specific matter (genec? hpa? someone else?) in order 
> to guide you more specifically.
Please!

-- 
Mathieu Chouquet-Stringer                               m+syslinux at thi.eu.com
            The sun itself sees not till heaven clears.
	             -- William Shakespeare --

Hello Hans Peter,

Any idea on how I could debug this problem? Basically lpxelinux 6.03
reboots while loading the initrd if its size is above a certain
threshold. It only happens on certain servers and there's not output
when it happens. I can trigger it reliably on affected hardware.

On Wed, May 22, 2019 at 05:45:20PM +0200, Mathieu Chouquet-Stringer via Syslinux
wrote:
> > I don't know how much relevant debug info you could actually get
when
> > using the "-dhcpinfo" option of linux.c32 (see the wiki for
details).
> 
> I'll give it a shot nonetheless...
Reading the doc, it's kinda useless to me because I don't even boot the
loaded kernel...

-- 
Mathieu Chouquet-Stringer                               m+syslinux at thi.eu.com
            The sun itself sees not till heaven clears.
	             -- William Shakespeare --

On June 18, 2019 12:34:35 PM PDT, Mathieu Chouquet-Stringer <m+syslinux at
thi.eu.com> wrote:
>	Hello Hans Peter,
>
>Any idea on how I could debug this problem? Basically lpxelinux 6.03
>reboots while loading the initrd if its size is above a certain
>threshold. It only happens on certain servers and there's not output
>when it happens. I can trigger it reliably on affected hardware.
>
>On Wed, May 22, 2019 at 05:45:20PM +0200, Mathieu Chouquet-Stringer via
>Syslinux wrote:
>> > I don't know how much relevant debug info you could actually
get
>when 
>> > using the "-dhcpinfo" option of linux.c32 (see the wiki
for
>details).
>> 
>> I'll give it a shot nonetheless...
>
>Reading the doc, it's kinda useless to me because I don't even boot
the
>loaded kernel...
Which servers, what threshold, what clients, what about pxelinux.0?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.