Okay, here's what I'm seeing on the 64-bit version, now, trying to boot Solaris 10 and later:
0 > do-boot : do-boot ( Empty ) 00000000ffe400e8: parse-bootargs ( Empty ) 00000000ffe400f0: halt? ( 0 ) 00000000ffe400f8: do?branch ( Empty ) 00000000ffe40148: get-bootdev ( Empty ) 00000000ffe40150: load-pkg ( Empty ) 00000000ffe40158: mount-root ( Empty ) 00000000ffe40160: zflag? ( 0 ) 00000000ffe40168: nested? ( 0 0 ) 00000000ffe40170: invert ( 0 ffffffffffffffff ) 00000000ffe40178: and ( 0 ) 00000000ffe40180: do?branch ( Empty ) 00000000ffe401a0: load-file : load-file ( Empty ) 00000000ffe3fef8: get-arch ( Empty ) 00000000ffe3ff00: ( ffe3e7c8 c ) 00000000ffe3ff08: open-path ( 0 ) 00000000ffe3ff10: loader-base ( 0 51000000 ) 00000000ffe3ff18: over ( 0 51000000 0 ) 00000000ffe3ff20: get-file : get-file ( 0 51000000 0 ) 00000000ffe3d760: dup ( 0 51000000 0 0 ) 00000000ffe3d768: >r ( 0 51000000 0 ) 00000000ffe3d770: ( 0 51000000 cabc000 ) 00000000ffe3d778: dup ( 0 51000000 cabc000 cabc000 ) 00000000ffe3d780: rot ( 0 cabc000 cabc000 51000000 ) 00000000ffe3d788: vmem-alloc-prop : vmem-alloc-prop ( 0 cabc000 cabc000 51000000 ) 00000000ffe3d620: 2dup ( 0 cabc000 cabc000 51000000 cabc000 51000000 ) 00000000ffe3d628: (lit) ( 0 cabc000 cabc000 51000000 cabc000 51000000 ffe39440 ) 00000000ffe3d638: catch ofmem_claim_phys - out of space (failed request for 000000000cabc000 bytes) ( 0 cabc000 cabc000 51000000 51000000 0 ) 00000000ffe3d640: do?branch ( 0 cabc000 cabc000 51000000 51000000 ) 00000000ffe3d718: nip ( 0 cabc000 cabc000 51000000 ) 00000000ffe3d720: nip ( 0 cabc000 51000000 ) 00000000ffe3d728: 0 ( 0 cabc000 51000000 0 ) 00000000ffe3d730: swap ( 0 cabc000 0 51000000 ) 00000000ffe3d738: (semis) [ Finished vmem-alloc-prop ] ( 0 cabc000 0 51000000 ) 00000000ffe3d790: rot ( 0 0 51000000 cabc000 ) 00000000ffe3d798: 2dup ( 0 0 51000000 cabc000 51000000 cabc000 ) 00000000ffe3d7a0: tuck ( 0 0 51000000 cabc000 cabc000 51000000 cabc000 ) 00000000ffe3d7a8: r> ( 0 0 51000000 cabc000 cabc000 51000000 cabc000 0 ) 00000000ffe3d7b0: ( 0 0 51000000 cabc000 cabc000 51000000 cabc000 0 ) 00000000ffe3d7b8: Unhandled Exception 0x0000000000000032 PC = 0x00000000ffd1c8a4 NPC = 0x00000000ffd1c88c Stopping execution
I'm not sure what's happening where the "ofmem_claim_phys - out of space" error occurs - I can pull up gdb, if that helps, and try to track down some more information.
I can't track down any of the errors for Solaris 9 and earlier right now, as a recent change in either qemu or openbios is causing it to fail to even load the fcode image:
Configuration device id QEMU version 1 machine id 32 CPUs: 1 x FMI,MB86904 UUID: 00000000-0000-0000-0000-000000000000 Welcome to OpenBIOS v1.0 built on Aug 11 2010 23:20 Type 'help' for detailed information
0 > boot cdrom -H Not a bootable ELF image Not a bootable a.out image No valid state has been set by load or init-program ok 0 > boot cdrom Not a bootable ELF image Not a bootable a.out image No valid state has been set by load or init-program ok
I'm happy to provide more information, do more debugging, etc.
-Nick
On 2010/08/10 at 02:57, Mark Cave-Ayland mark.cave-ayland@siriusit.co.uk
wrote:
Nick Couchman wrote:
After these latest changes, I get the following trying to boot Solaris 9:
Configuration device id QEMU version 1 machine id 32 CPUs: 1 x FMI,MB86904 UUID: 00000000-0000-0000-0000-000000000000 Welcome to OpenBIOS v1.0 built on Aug 9 2010 23:27 Type 'help' for detailed information
Trying cdrom:d... Not a bootable ELF image Loading a.out image... Loaded 7680 bytes entry point is 0x4000 bootpath: /iommu/sbus/espdma/esp/sd@2,0:d
Jumping to entry point 00004000 for type 00000005... switching to new context: bootblk: can't find the boot program halt, power off
My boot command line looks like this: ./sparc-softmmu/qemu-system-sparc -hda disk0.img -cdrom
/media/Sun-ISOs-2/solaris-9/software1.iso -bios ../openbios-devel/obj-sparc32/openbios-builtin.elf.nostrip -nographic -boot d
-Nick
Hi Nick,
I don't think I've ever tested Solaris with OpenBIOS SPARC32 (although I have been told we may have some Solaris 8 CDs lying around somewhere if they would do the job?). Is this just an update, or are you reporting a regression? If it's a regression, can you do an SVN bisect?
ATB,
M-D.
-------- 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.