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 EFLAGS=00000206 Can somebody interpret the register dump? Any other idea? Thank you. Regards, Fred
Good day, Fred! You might try subscribing to the mailing-list, where you will find at least three responses to your last e-mail. If it helps, their dates are: - November 8th - November 8th - November 9th And your http://reboot.pro post also had at least one response. - Shao Miller
In the http://reboot.pro Syslinux forum, On 11/30/2012 12:17, artreader at gmx.net wrote:> @Wonko the Sane: the MBR is correct and it is the syslinux one. With non HP threre is no problem. > @Shao: Syslinux is installed with linux sysinstall sucessfully and it is the _boot_ with syslinux, which makes a problemThank you for clarifying whether it was the install or the boot. Perhaps we can determine if it is the MBR or if it's Syslinux that's causing the problem. If you leave the Syslinux MBR intact but use some other boot code on the partition's boot sector (such as DOS or Windows), does the red screen still occur? If it does, then the Syslinux MBR could be the problem. If it doesn't, then it could be Syslinux that's causing the problem. If you cannot perform this test because you do not have DOS or Windows involved, please let us know. It's possible that someone can come up with a diagnostic partition boot sector for you, if there isn't one already. As far as understanding the red screen's output, I think we'd really need an _exact_ version access to the corresponding files in the build tree. If you are using one of the downloads, then please specify exactly which one (the download link). However, if you are certain that the red screen has the _exact_ same output regardless of 4.06 or 5.00, then perhaps we'll find that the MBR is the problem. Or not. - Shao Miller
On 11/30/2012 05:33 AM, artreader at gmx.net wrote:> 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. >This happens on *install* or on *boot*? If it happens on install, using what installer? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
Hi Peter> > 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. > > > > This happens on *install* or on *boot*? >This happens on boot, only on boot. Thank you, Fred
Hi Shao, thank you for the detailed questions.> > To make sure there is no "foreing" code in partition table and MBR, > > MBR was nulled with mbr-sys and partition table produced new with fdisk. > > Meaning the Syslinux MBR code is destroyed, right? >Meaning the "old" MBR code had been destroyed before the new MBR code was created by syslinux> > Cause it is a machine with HP Raid, the old-fashioned cciss driver aund > the new one hpsa were tested. The FAT Partition created with parted and > than syslinux install. > > > > But did your "syslinux install" command re-install the Syslinux MBR code > again, or not? What was your command, please? >syslinux -f -U /dev/sda1 (with hpsa driver) syslinux -f -U /dev/cciss/cod0p1 (with cciss driver)> > > > So, from the logical part, it should be syslinux, that makes the > problem. > > > > What I was asking about was whether or not we could determine which of > the following items might be responsible: > > 1. The Syslinux convenience MBR code that can be installed with the > Syslinux installer > > 2. The Syslinux volume boot record code that can be installed with the > Syslinux installer >To complete the description the whole script sequence for hpsa driver: fdisk /dev/sda < "w\no\n" mbr-sys -z /dev/sda parted -s /dev/sda mklabel msdos parted -s /dev/sda mkpart primary fat16 0 700 parted -s /dev/sda mkfs 1 fat16 parted -s /dev/sda set 1 boot on partprobe syslinux -f -U /dev/sda1 For cciss: fdisk /dev/cciss/c0d0 < "w\no\n" mbr-sys -z /dev/cciss/c0d0 parted -s /dev/cciss/c0d0 mklabel msdos parted -s /dev/cciss/c0d0 mkpart primary fat16 0 700 parted -s /dev/cciss/c0d0 mkfs 1 fat16 parted -s /dev/cciss/c0d0 set 1 boot on partprobe syslinux -f -U /dev/cciss/c0d0p1> > For the 4.06 release a tarball syslinux-4.06.tar.bz2 from > http://www.kernel.org/pub/linux/utils/boot/syslinux/ was downloaded. > > Thank you for this information. -^ This specifies the binary code that > was used. > > > Before I tried 4.03, 3.86 etc from the same source. > > For 5.00 pre 12 a snapshot from > http://git.kernel.org/?p=boot/syslinux/syslinux.git was obtained. > > Because the same source code can build very different binary code on > different systems, specifying the source code is not very useful for > troubleshooting a dump that is binary-specific; the binary code is > needed.ldlinux.elf und syslinux binaries are attached. 4.06 is built statically, 5.00 - dynamically> > Could you possibly clarify about your MBR test? It might be nice to > avoid digging into the the red screen dump by getting the simple stuff > out of the way, first. >Regards, Fred Feuerstein
On 11/30/2012 08:33, artreader at gmx.net wrote:> > 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 >Do you happen to know the disk's sector-size, from the HP unit's BIOS' perspective, by any chance? - Shao