[syslinux] [5.xx-6.01] broken PXE with HTTP

H. Peter Anvin hpa at zytor.com
Mon Jul 8 14:32:04 PDT 2013


On 07/05/2013 01:02 PM, Gerardo Exequiel Pozzi wrote:
> 
> 5.00      [pxelinux.0]  OK 5.01      [pxelinux.0]  OK 5.02-pre1
> [pxelinux.0]  OK 5.02-pre2 [pxelinux.0]  OK 5.02-pre3 [pxelinux.0]
> BAD (freeze, no error messages, 100% CPU used)
> 
> 5.10-pre1 [pxelinux.0]  BAD (freeze, no error messages, 100% CPU
> used) 5.10-pre2 [pxelinux.0]  BAD (Failed to load: ldlinux.c32,
> Boot failed:) 5.10      [pxelinux.0]  BAD (Failed to load:
> ldlinux.c32, Boot failed:)
> 
> 6.00      [pxelinux.0]  BAD (Failed to load: ldlinux.c32, Boot
> failed:) 6.01      [pxelinux.0]  BAD (Failed to load: ldlinux.c32,
> Boot failed:)
> 
> 
> 5.10-pre1 [lpxelinux.0] BAD (freeze, no error message, cpu idle) 
> 5.10-pre2 [lpxelinux.0] BAD (no error message, Boot failed:) 5.10
> [lpxelinux.0] BAD (no error message, Boot failed:)
> 
> 6.00      [lpxelinux.0] BAD (no error message, Boot failed:) 6.01
> [lpxelinux.0] BAD (no error message, Boot failed:)
> 
> 
> OK: implies that pxelinux tries to retrive others files like
> ldlinux.c32 BAD: no more files are retrived, there is not attemp at
> least to GET any file from server.
> 
> Maybe something wrong with b208ba467f678ed8e73f8d11fc0609634120cb83
> ?
> 

So we have a bit of a special situation here... iPXE is used to
download lpxelinux.0 via HTTP, and then we need to pick up and use
HTTP protocol.

What hardware is this, and do you know what iPXE build?

There seem to be odd interactions between iPXE and the lwip code.
Unfortunately iPXE version numbers are useless, so it is hard to track
down specifics.

	-hpa



More information about the Syslinux mailing list