On Thu, Dec 10, 2009 at 1:02 AM, Igor Kovalenko igor.v.kovalenko@gmail.com wrote:
On Thu, Dec 10, 2009 at 12:47 AM, Mark Cave-Ayland mark.cave-ayland@siriusit.co.uk wrote:
Igor Kovalenko wrote:
Well qemu's crash is a bug in qemu for sure. The garbage being written is probably due to device i/o mapping issues (could clash with physical ram mapped low) so is separate issue. Of course we will need to solve both :) Do you see screen garbage before crash?
Yeah; a keyboard command error and a single letter "s" with -nographic:
qemu: unsupported keyboard cmd=0x57 sSegmentation fault
Do you run in graphics mode at all? The garbage I see is in qemu screen, due to framebuffer being mapped where data is loaded by milax code.
The segmentation fault is actually the Qemu host process dying. The VNC display looks more interesting; it seems that something is writing all over the screen memory just before the crash happens.
I believe from Nick's email that he can also recreate this using latest OpenBIOS SVN, a recent pull of Qemu and a Milax 0.3.2 ISO image.
Please try this patch as well, helps clearing a few subtle memory issues.
openbios-forth-package-prevent-null-dereferences
- Prevent dereferencing page zero and complain about invalid handles
Signed-off-by: igor.v.kovalenko@gmail.com