Syslinux - May 2009 - pxelinux.bin (3.80) hanging at the beginning of menu.c32 TFTP transfer

Hi,

Using syslinux 3.80, I'm seeing pxelinux.bin hanging after the
(succesfull) transfer of the default file.
Running a lan trace, it appears that all goes fine until the time
pxelinux sends a TFTP RRQ for menu.c32 to the TFTP server, gets the
first data packet back, and apparently freezes at this point.
The TFTP server then times out and retries (3 times) then finally
sends an error packet with an ErrMsg of "time out".
Using 3.80, the client machine is frozen, but keyboard interrupts are
still processed, and Ctrl-Alt-Del reboots.
Using 3.72, I get similar results, but with keyboard interrupts stuck
(the machine needs hard reset or power cycling).

The TFTP service involved doesn't support tsize, but studying the the
release notes indicate that pxelinux handles this situation since
3.70.
Finally, in case this could help diagnosing the problem, I have
recorded a LAN trace that shows the whole client / tftp server dialog
since pxelinux startup, up to and including the final retries and
error message.

Is there anything else I could do to help diagnose that problem?

TIA,

Phil.

Philippe Auphelle wrote:
> Hi,
> 
> Using syslinux 3.80, I'm seeing pxelinux.bin hanging after the
> (succesfull) transfer of the default file.
> Running a lan trace, it appears that all goes fine until the time
> pxelinux sends a TFTP RRQ for menu.c32 to the TFTP server, gets the
> first data packet back, and apparently freezes at this point.
> The TFTP server then times out and retries (3 times) then finally
> sends an error packet with an ErrMsg of "time out".
> Using 3.80, the client machine is frozen, but keyboard interrupts are
> still processed, and Ctrl-Alt-Del reboots.
> Using 3.72, I get similar results, but with keyboard interrupts stuck
> (the machine needs hard reset or power cycling).
> 
> The TFTP service involved doesn't support tsize, but studying the the
> release notes indicate that pxelinux handles this situation since
> 3.70.
> Finally, in case this could help diagnosing the problem, I have
> recorded a LAN trace that shows the whole client / tftp server dialog
> since pxelinux startup, up to and including the final retries and
> error message.
> 
> Is there anything else I could do to help diagnose that problem?
> 
Could you try 3.81-pre10 from the Testing directory?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

Op 20090601 om 14:17 schreef Miller, Shao:
> Hey Phillipe, is it too much to disclose the name of this particular PXE
> service which PXELINUX seems to be having difficulty with?  - Shao

Thing I would like to known is
if pxelinux.0 from Syslinux 3.82 works with that server.
>From the release notes of version 3.82
        * PXELINUX: handle TFTP servers which have extra NULs at the
          end of an OACK packet.        


Cheers
Geert Stappers