[OpenBIOS] Faulty Qemu SPARC64 IDE emulation?
Nick.Couchman at seakr.com
Wed Dec 9 22:42:23 CET 2009
> 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?
No, I don't really see any garbage. If I boot without any debugging at all, I see the following:
OpenBIOS for Sparc64
Configuration device id QEMU version 1 machine id 0
CPUs: 1 x SUNW,UltraSPARC-II
Welcome to OpenBIOS v1.0 built on Dec 9 2009 19:06
Type 'help' for detailed information
0 > boot cdrom
[sparc64] Booting file 'cdrom' with parameters ''
Not a bootable ELF image
Not a Linux kernel image
Not a bootable a.out image
Loading FCode image...
Loaded 7084 bytes
entry point is 0x4000
qemu: unsupported keyboard cmd=0x57
The only things of interest are 1) that it's referencing a keyboard command with the error really seems to be in the IDE code, and 2) that there's an extra "s" before the segmentation fault. This probably confirms Mark's suspicion that the IDE code is writing to the wrong memory segment - perhaps to the keyboard segment, as Qemu generates a keyboard error and an extra character. I don't know if that's technically considered garbage or not...
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.
More information about the OpenBIOS