similar to: Illegal OpCode on PXE exit with syslinux-6.0{1,2}

On Fri, 19 Jul, at 02:34:04PM, Igor Sverkos wrote: > Hi, > > while testing syslinux-6.01_pre6 and syslinux-6.02_pre5 I noticed an > illegal OpCode error on PXE exit. Urgh, not good. Do you see the same error with 5.11-pre8? -- Matt Fleming, Intel Open Source Technology Center

Hi, > Do you see the same error with 5.11-pre8? Yes, I do :( -- Regards, Igor

Hi, > Have you ever successfully used this config file with 4.06 or earlier? Mh, no. And I'll get the illegal opcode on 4.06 exit for local boot as well. Not sure if it has something to do with the fact, that there is no local bootloader, syslinux can start (it is a new system where's currently no OS installed). The config itself was grabbed from various PXE boot tutorials, for

Using the latest version of syslinux/pxelinux.. When cold pxe booting a HP DL585 G2 (Broadcom NIC), if the pxemenu item is LOCALBOOT 0 and is selected, then a red screen with the following error occurs: Illegal OpCode EAX=000E09AC EBX=00000000 ECX=00000000 EDX=00000000 EBP=00004408 ESI=0000F000 EDI=000045E9 DS=F000 ES=0000 FS=0000 GS=0003 CS:EIP=1000:00000240

Hi to all, While trying to install syslinux on small (700 MB) FAT16 Partition on HP Server got Red Screen of Death with a register dump. Illegal OpCode EAX=00001F01 EBX=000001A4 ECX=00000000 EDX=00000019F EBP=0000FBFA ESI=000007BE EDI=00000800 DS=0000 ES=0000 FS=0000 GS=0000 CS:EIP=0000:000083A6 SS:ESP=1000:0000AFF6 EFLAGS=00000206 Tested many versions of syslinux: from 3.63 to 4.06:

Hi to all, from syslinux 4.06 and 5.00 pre 12 came the same dump. Background: While trying to install syslinux on small (700 MB) FAT16 Partition on HP Server got Red Screen of Death with a register dump. Illegal OpCode EAX=00001F01 EBX=000001A4 ECX=00000000 EDX=00000019F EBP=0000FBFA ESI=000007BE EDI=00000800 DS=0000 ES=0000 FS=0000 GS=0000 CS:EIP=0000:000083A6 SS:ESP=1000:0000AFF6

This just came up on IRC, 15:01 < chithead> the first one that fails is ld -m elf_i386 -Wl,-O1 -Wl,--as-needed -Bsymbolic -pie -E --hash-style=gnu -T /var/tmp/portage/sys-boot/syslinux-6.01_pre5/work/syslinux-6.01-pre5/core/i386/syslinux.ld -M -o ldlinux.elf ldlinux.o \ 15:01 < chithead> --start-group libcom32.a --whole-archive

Hi, > What steps are you using to recompile the releases? Are you working from > git? No, not git. See http://www.syslinux.org/archives/2013-July/020543.html and the f'up from Ady and my response regarding re-compiling. So actual I think I don't re-compile everything. I think I am using the pre-build modules from your provided archives (if 'make installer && make

Hi, well, I was finally able to build syslinux-5.11-pre8 from git, but the system doesn't boot with the self-compiled version. All I see is: http://666kb.com/i/cfplluqpcy6owptq3.jpg Build log can be found in http://www.syslinux.org/archives/2013-July/020452.html After I installed the self-compiled syslinux version, I run this commands: # cd /boot/extlinux # rm -rf *.c32 # extlinux

Hi, 6.02-pre8 still doesn't work. Same error. Nothing happens, no menu. Did you change something on the build system between pre5 and pre6? -- Regards, Igor

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

Hello! I got oops after about 3 hours of uptime. Load was about 1,5. This is output of ksymoops after forced reboot if it helps someone. :-) ksymoops 2.4.0 on i686 2.4.14-pre8. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.14-pre8/ (default) -m /boot/System.map-2.4.14-pre8 (default) Warning (compare_maps): mismatch on

On 07/11/2013 01:38 PM, Igor Sverkos wrote: > Hi, > > OK, I solved the problem. Before calling "make installer", I first > have to call "make spotless" and "make". Then I can call "make > installer". > > Is that documented, somewhere? > That would be a bug. The documented sequence is "make clean", "make

On 07/01/2014 09:55 PM, Gene Cumm wrote: > On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 ... > > Odd. 4.07 should be good but the 4.10/5.1*/6.0* revisions make sense. My bad. I tried again, and in 4.07 we do get further. We couldn't boot all the way because, it seems, using

When running test 5 in Memtest86+ v1.65, I got a "this opcode is not supported", so I decided to add it. It''s a compare operation, and it''s just the opposite of the already supported one (opcode 0x39), so it''s nothing spectacular. Why there''s a page-fault when this instruction gets executed, I haven''t got a clue, but I have a feeling that

Hello, I have lots of the following entries in my log: nmbd[1605]: [2010/05/28 09:59:51, 0] nmbd/nmbd_packets.c:validate_nmb_packet(1375) nmbd[1605]: validate_nmb_packet: Bad REG/REFRESH Packet. validate_nmb_packet: Ignoring request packet with opcode 5. What does this mean exactly? Can I ignore this? I use samba (sernet-samba) 3.3.12-25 on Debian Lenny. Thanks and Regards. Henry

Hello, I have an issue with ebtables --arp-opcode and vlan support on the bridge. Ebtables support --arp-opcode witch is used for arp manipulation. ebtables -t nat -A PREROUTING -p arp --arp-opcode Request -j arpreply --arpreply-mac 10:11:12:13:14:15 --arpreply-target ACCEPT -i eth1 But it does not work when Ethernet frame comes tag with vlan pid. Can i overcome this limitation? Fanks

Currently the mmio_operands assumes writing to memory when operand 0 is register or immediate, this is false for cmp/test opcode. This patch resolve this problem, please review. Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> Thanks Yunhong Jiang _______________________________________________ Xen-devel mailing list

Your message dated Sat, 10 Dec 2011 20:00:59 +0100 with message-id <20111210190059.GG15557 at wavehammer.waldi.eu.org> and subject line no bug has caused the Debian Bug report #649141, regarding xen-hypervisor-4.0-amd64: live migration fails with invalid opcode due to nonstop_tsc to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

On Thu, Feb 13, 2014 at 2:15 AM, Kui Zhang <kuizhang at gmail.com> wrote: > Hello, > > When CONFIG_DRM_NOUVEAU=y, I get following error. Blank screen after initrd. > > This was in the dmesg. > > [ 0.282559] [drm] hdmi device not found 1 0 1 > [ 0.282688] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046800a3 > [ 0.282693] nouveau [ DEVICE][0000:01:00.0]