[OpenBIOS] Qemu/OpenBIOS 64-bit

[Tarl Neustaedter]

On 2013-Dec-27, 19:08 , Nick Couchman wrote:
> [root at qemu-openbios-dev ~]# /opt/qemu/bin/qemu-system-sparc64 -cdrom /mnt/iso/Solaris/sol-10-u9-ga-sparc-dvd.iso -boot d -nographic -m 2048
> OpenBIOS for Sparc64
> Configuration device id QEMU version 1 machine id 0
> kernel cmdline
> CPUs: 1 x SUNW,UltraSPARC-IIi
> UUID: 00000000-0000-0000-0000-000000000000
> Welcome to OpenBIOS v1.1 built on Dec 27 2013 23:00
>    Type 'help' for detailed information
> Trying cdrom:f...
> Not a bootable ELF image
> Not a bootable a.out image
>
> Loading FCode image...
> Loaded 7420 bytes
> entry point is 0x4000
> Ignoring failed claim for va 1000000 memsz a8cb6!
> Ignoring failed claim for va 1402000 memsz 4b4a8!
> Ignoring failed claim for va 1800000 memsz 61b48!

Those are a problem. My recollection is that it's loading Solaris 
(genunix) in at 100.0000. Failing those claims means something is busted 
with the memory model.

>
> Jumping to entry point 00000000010071d8 for type 0000000000000001...
> switching to new context: entry point 0x10071d8 stack 0x00000000ffe86a01
> warning:interpret: exception -13 caught

That's a problem. No idea what an exception -13 means. I'm surprised it 
was able to continue after that.

> SunOS Release 5.10 Version Generic_142909-17 64-bit
> Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
> spacex@:interpret: exception -13 caught

spacex@ is an forth operation to do a 64-bit load from an arbitrary 
address space. Most of them are used to access physical memory, for 
things like manipulating MMUs, although there are a few for dealing with 
some of the IO devices. This sounds like somewhere QEMUs machine model 
doesn't directly match what Solaris 5.10 thinks it should.

> could not find debugger-vocabulary-hook>threads:interpret: exception -13 caught
> (Can't load tod module) EXIT

That looks like Solaris is trying to panic, and something had trashed 
the forth vocabulary. Debugger-vocabulary-hook is a defer word in 
openboot which is invoked on enter-forth, I suspect the >threads is from 
Solaris' forthdebug module.