"Gregg C Levine" <[EMAIL PROTECTED]> writes: > Hello from Gregg C Levine normally with Jedi Knight Computers > I just tried to create an elf bootable image, using the contents of > mkelfImage-1.12.tar.gz, it caused what looked like a kernel panic when I > entered these commands from a remote Xterm, "./kexec kernel.elf". It > printed out the usual message that of the kernel exec function at work, > and the it bombed. It then caused the kernel panic, complete with the > contents of the register contents being printed out. Exactly as if the > computer was told to activate an interrupt, but there wasn't a handler > set up at that address. This is not the usual panic, that I see when > invoking the kernel exec function caused by the mkelfImage function > being run over a kernel, as supplied by, say a different version. Please > note, that I can not supply any further data at this time.
That is o.k. I have a fair guess of what is happening. The latest versions of mkelfImage attempt to detect LinuxBIOS by finding the LinuxBIOS table. And if it doesn't find it it assumes that you are running on a pcbios. And does 16bit interrupt calls to get the information it wants instead. Actually that doesn't explain it as it loads an ldt first so the kernel should not have a chance to execute. All I know is that there are some very strange machines out there. You can slightly edit the code to give you lots of debugging output over the serial port if you need/want to. > Eric, a different question. I came across a patch, mkelfImage-1.12.diff. Just to show what I was doing. The differences from one version to the next. So mkelfImage-1.12.diff are the differences from 1.11 to 1.12. > Also some of the other ones also have diff files, patches, available for > them, what prompted them? I just felt it was good form. Eric
