On 28/12/13 00:08, Nick Couchman wrote:
[root@qemu-openbios-dev ~]# /opt/qemu/bin/qemu-system-sparc64 -cdrom /mnt/iso/Solaris/sol9-software1.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 5936 bytes entry point is 0x4000 open isn't unique.
Jumping to entry point 0000000000100000 for type 0000000000000001... switching to new context: entry point 0x100000 stack 0x00000000ffe86a01 warning:interpret: exception -13 caught SunOS Release 5.9 Version Generic 64-bit Copyright 1983-2002 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.
panic[cpu0]/thread=140a000: VAC too big!
00000000014098c0 unix:startup_modules+118 (12000, 142a400, 30000018000, 103, 78004000, 1430800) %l0-3: 0000000000000103 0000000000000000 000000000140c000 00000000014175a8 %l4-7: 00000000014175b8 0000000078004000 0000000000002000 0000000000012020 0000000001409970 unix:startup+1c (0, 20, 78002000, 2000, 1400000, 0) %l0-3: 000000000140b400 000000000140b400 0000000001477c00 0000000000002000 %l4-7: 00000000000c36c5 0000000000000000 0000000000003f61 000000000147d848 0000000001409a20 genunix:main+4 (1409ba0, ffd0cad8, 1409ec0, 325b5f, 2000, 500) %l0-3: 000000000140b400 0000000000000000 0000000001412a28 0000000078002000 %l4-7: 000000000140a000 0000000000326000 000000000147fd60 000000000105e938
skipping system dump - no dump device configured rebooting... BOOTpanic - kernel: prom_reboot: reboot call returned! EXIT
I see the "VAC too big!" error on my local copy of 32-bit Solaris 9 too. Some searching showed the message occurs in the OpenSolaris source at http://fxr.watson.org/fxr/source/sfmmu/vm/hat_sfmmu.c?v=OPENSOLARIS#L1347.
I'm not exactly sure what this is trying to check here, but I do know that OpenBIOS uses 512K PTEs to map itself, while calls to OFMEM use 8K PTEs which may be relevant. Does anyone know the exact significance of this?
ATB,
Mark.