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
On Jul 8, 2013 5:34 PM, "H. Peter Anvin" <hpa at zytor.com> wrote:> 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?qemu-1.5.1; iPXE likely from the same. Matches commit 09c5109b> 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.The only specifics I recall seeing in packet captures is that even though lwIP is using UNDI to open a TCP socket on a port, iPXE steps in and says that port is closed. -- -Gene
On 07/09/2013 10:41 AM, Gene Cumm wrote:> On Jul 8, 2013 5:34 PM, "H. Peter Anvin" <hpa at zytor.com> wrote: >> 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? > > qemu-1.5.1; iPXE likely from the same. Matches commit 09c5109bRight. Also happens between two real hardware. Where iPXE ROM [rtl8136] (v1.0.0-1241-g936134e) is chainloaded (ipxe.lkrn) via syslinux-4.06. Packet capture is uploaded at [#1] (tcpdump -i enp0s16 -w dump.cap 'host 192.168.0.242') [#1] https://dl.dropboxusercontent.com/u/88891866/dump_syslinux-6.01_ipxe-936134e.cap.xz [#2] https://dl.dropboxusercontent.com/u/88891866/dump_syslinux-6.01_ipxe-936134e.cap.xz.sig> >> 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. > > The only specifics I recall seeing in packet captures is that even > though lwIP is using UNDI to open a TCP socket on a port, iPXE steps > in and says that port is closed. > > -- > -Gene > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > Please do not send private replies to mailing list traffic. > >-- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: <http://www.zytor.com/pipermail/syslinux/attachments/20130709/8dbd69b2/attachment.sig>
On 07/09/2013 06:41 AM, Gene Cumm wrote:> > The only specifics I recall seeing in packet captures is that even > though lwIP is using UNDI to open a TCP socket on a port, iPXE steps > in and says that port is closed. >Right, and that is death right there. I need to talk to Michael and see if this can be worked around. -hpa