Additional information: I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. So memtest 4.1 and 4.2 worked with pxelinux 4.06 Peter> Date: Fri, 28 Jun 2013 09:02:30 +0100 > From: matt at console-pimps.org > To: coolpet80 at hotmail.com > CC: syslinux at zytor.com > Subject: Re: [syslinux] pxelinux 5.x, 6.x memtest problem > > On Fri, 28 Jun, at 08:13:03AM, N?meth P?ter wrote: > > Hi guys! > > I tried to boot memtest86+ v4.2 (renamed memtest.bin to memtest), and > > i have issues to boot it with pxelinux 5.x and greater.Pxelinux 4.06 > > works fine both memtest 4.1 and 4.2. > > With version 6.00 no error message caught, only writes out dots. Any > > keypress does a reboot.With version 5.01 the error message is the > > follow:Loading images/memtest/memtest86... okBooting kernel failed: > > Bad file number > > The pxelinux.cfg/default file contents:DEFAULT memtest2 > > LABEL memtest KERNEL images/memtest/memtest.original APPEND console=ttyS0,9600n8 > > LABEL memtest2 KERNEL images/memtest/memtest86 APPEND console=ttyS0,9600n8 > > PROMPT 1TIMEOUT 100 > > Any ide how to solve this? > > This is the infamous PXE-stack-smasher-bug. It's a regression in the > 5.xx series (which means it's also in the 6.xx series). This has been > one of those difficult to reproduce bugs, because it's very much > dependent on the BIOS memory map. > > Is anyone that is hitting this issue willing/able to build PXELINUX from > a git branch to help with debugging this? > > -- > Matt Fleming, Intel Open Source Technology Center
> Additional information: > I was tried it with 2 virtualbox (version 4.2.14r86644).1rst: debian weezy with isc-dhcp-server, pxelinux5.01, pxelinux 6.00, tftp-hpa2nd: empty virtualbox booting from virtual network card. > So memtest 4.1 and 4.2 worked with pxelinux 4.06 > Peter >Yes, memtest boots from all variants of Syslinux 4.06. But, in Syslinux 4.06, there is linux.c32, which is a sort of introduction to Syslinux 5.xx (please allow me to be not strictly accurate in this sentence in this context). Booting with any variant of Syslinux 4.06, but using linux.c32, memtest would fail, which indicated some kind of problem related to the status of Syslinux 5.xx at the time v4.06 was released. According to your report, you also see the "Booting kernel failed: Bad file number", which might have been fixed already. So, I would suggest for you to try again with the latest testing 5.11-preN, and/or 6.01-preM that you can find available, or to wait for the next stable release and then report again. Regards, Ady.
On Fri, Jun 28, 2013 at 10:13 AM, Ady <ady-sf at hotmail.com> wrote:> But, in Syslinux 4.06, there is linux.c32, which is a sort of > introduction to Syslinux 5.xx (please allow me to be not strictly > accurate in this sentence in this context). > > Booting with any variant of Syslinux 4.06, but using linux.c32, > memtest would fail, which indicated some kind of problem related to > the status of Syslinux 5.xx at the time v4.06 was released.PXELINUX 4.06 with Memtest86-4.20 and Memtest86+-4.20 binaries (renamed) using LINUX directly works. Using linux.c32: "syslinux_boot_linux() failed: Error 0" PXELINUX 5.10, 5.11-pre3, 6.01-pre5 with binaries LINUX directly: "Booting kernel failed: Invalid argument" -- -Gene