Re: [GXemul-users] problems running OpenBSD/mvme88k on gxemul

[George K. <xke...@ne...>]

In trunk (r5803), the new mode "mvme187" and the legacy mode "mvme187" 
have the same name. This is the first problem. The new mode is not 
complete enough to work. You need the legacy mode.

So I renamed the legacy "mvme187" to "oldmvme187".

Apply my attached patch to trunk:
$ cd gxemul
$ patch < oldmvme187.diff

Compile it again. Now you can run trunk, but you must use -e oldmvme187 
and not -e mvme187.

There is a second problem. I tried to boot OpenBSD/mvme88k 5.2 and 
reproduced your MODE_SENSE messages and your stuck boot. (I never got 
your malloc error, perhaps because my host machine runs OpenBSD/amd64 
5.2, so I have bsd libc, not glibc.)

No one has fixed the second problem.

==snip==
$ gxemul -e oldmvme187 -d vme.hd -d b:openbsd_mvme88k_5.2.iso -j 
5.2/mvme88k/bsd.rd
GXemul (unknown version)    Copyright (C) 2003-2012  Anders Gavare
Read the source code and/or documentation for other Copyright messages.

Simple setup...
     net:
         simulated network: 10.0.0.0/8 (max outgoing: TCP=100, UDP=100)
         simulated gateway+nameserver: 10.0.0.254 (60:50:40:30:20:10)
         simulated nameserver uses real nameserver 192.168.10.1
     machine:
         memory: 64 MB
         cpu0: 88100
         machine: MVME187
         diskimage: vme.hd
             SCSI DISK id 0, read/write, 2048 MB (4194304 sectors)
         diskimage: openbsd_mvme88k_5.2.iso
             SCSI CD-ROM id 1, read-only, 313 MB (641992 sectors) (BOOT)
         ISO9660 boot:
             "CDROM":5.2/mvme88k/bsd.rd
             extracted 3305741 bytes into /tmp/gxemul.frsosdylKvdS
         loading /tmp/gxemul.frsosdylKvdS
         removing /tmp/gxemul.frsosdylKvdS
         cpu0: starting at 0x00010020

NOTE: This is a LEGACY emulation mode.

-------------------------------------------------------------------------------

CPU0 is associated to 2 MC88200 CMMUs
Copyright (c) 1982, 1986, 1989, 1991, 1993
         The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org

OpenBSD 5.2 (RAMDISK) #50: Wed Jul 25 21:24:31 GMT 2012
ro...@ar...:/usr/src/sys/arch/mvme88k/compile/RAMDISK
real mem = 67108864 (64MB)
avail mem = 59473920 (56MB)
mainbus0 at root: Motorola MVME187, 33MHz
cpu0: M88100 rev 0x3, 2 CMMU
cpu0: M88200 (16K) rev 0x9, full Icache, M88200 (16K) rev 0x9, full Dcache
pcctwo0 at mainbus0 addr 0xfff00000: rev 0
nvram0 at pcctwo0 offset 0xc0000: MK48T08
cl0 at pcctwo0 offset 0x45000 ipl 3: console
osiop0 at pcctwo0 offset 0x47000 ipl 2: NCR53C710 rev 2, 66MHz
scsibus0 at osiop0: 8 targets, initiator 7
osiop0: target 0 ignored sync request
osiop0: target 0 now using 8 bit asynch xfers
sd0 at scsibus0 targ 0 lun 0: <GXemul, vme.hd, 0> SCSI2 0/direct fixed
sd0: 2048MB, 512 bytes/sector, 4194305 sectors
[ MODE_SENSE for page 8 is not yet implemented! ]
[ MODE_SENSE for page 8 is not yet implemented! ]
[ unknown MODE_SELECT: cmd = 15 10 00 00 63 00, data_out = 00 00 00 08 
00 00 00 00 00 00 02 00 ]osiop0: target 1 ignored sync request
osiop0: target 1 now using 8 bit asynch xfers
cd0 at scsibus0 targ 1 lun 0: <GXemul, openbsd_mvme88k, 0> SCSI2 5/cdrom 
removable
vme0 at pcctwo0 offset 0x40000
vme0: using BUG parameters
vme0: vme to cpu irq level 1:1
vmes0 at vme0
boot device: <unknown>
osiop0: target 0 now using 8 bit asynch xfers
root on rd0a swap on rd0b dump on rd0b
WARNING: clock gained 248 days -- CHECK AND RESET THE DATE!
==snip==

Here, the emulator is stuck. I enabled tracing (like you did with 
OpenBSD 4.7 and 4.6) but got an infinite trace like yours.
--George Koehler