Re: installing openbsd/vax on simh-vax
Darren Clark <[email protected]> Sat, 06 Oct 2012 09:48:45 -0400
| Newsgroups | gmane.os.openbsd.vax |
|---|---|
| Message-ID | <[email protected]> |
Hello,
Can you please post your VAX.INI file for SimH.
On 10.05.2012 11:21 PM, YASUOKA Masahiko wrote:
> Hi,
>
> I'm trying to install OpenBSD 5.1/vax on simh-vax. I installed it
> successfully, but boot failed with "panic: cannot open disk,
> 0x900/0x902, error 6".
>
> I'm following instructions written in
> http://www.openbsd.org/vax-simh.html .
>
> % sysctl kern.version
> kern.version=OpenBSD 5.2-current (GENERIC.MP) #8: Fri Oct 5 13:10:06 JST 2012
> [email protected]:/home/yasuoka/source/openbsd/src/sys/arch/i386/compile/GENERIC.MP
> % pkg_info -c simh
> Information for inst:simh-3.9.0p0
>
> Comment:
> PDP, IBM 1401, Nova and other CPUs simulator
>
>
> % sudo simh-vax openbsd.simh
>
> VAX simulator V3.9-0
> NVR: buffering file in memory
> Eth: opened OS device msk0
> Loading boot code from /usr/local/lib/simh/vax/ka655x.bin
>
>
> KA655-B V5.3, VMB 2.7
> Performing normal system tests.
> 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
> 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
> 08..07..06..05..04..03..
> Tests completed.
>>>> boot DUA0:
> (BOOT/R5:0 DUA0
>
>
>
> 2..
> -DUA0
> 1..0..
>
>
>>> OpenBSD/vax boot [1.16]<<
>>> Press enter to autoboot now, or any other key to abort: 0
>> boot bsd
> 1805672+63328+434840+[127380+157435]=0x277ff3
> [ using 284815 bytes of bsd a.out symbol table ]
> 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.1 (GENERIC) #46: Tue Feb 14 12:17:31 MST 2012
> [email protected]:/usr/src/sys/arch/vax/compile/GENERIC
> MicroVAX 3800/3900 [0A000006 01530302]
> cpu: KA655, CVAX microcode rev 6 Firmware rev 83
> real mem = 67043328 (63MB)
> avail mem = 61378560 (58MB)
> mainbus0 at root
> ibus0 at mainbus0
> uba0 at ibus0: Q22
> dz0 at uba0 csr 160100 vec 196 ipl 17
> mtc0 at uba0 csr 174500 vec 508 ipl 17
> mscpbus0 at mtc0: version 5 model 3
> mscpbus0: DMA burst size set to 4
> mt0 at mscpbus0 drive 0: TK50
> mt1 at mscpbus0 drive 1: TK50
> mt2 at mscpbus0 drive 2: TK50
> mt3 at mscpbus0 drive 3: TK50
> uda0 at uba0 csr 172150 vec 504 ipl 17
> mscpbus1 at uda0: version 3 model 3
> mscpbus1: DMA burst size set to 4
> ra0 at mscpbus1 drive 0: RA92
> ra1 at mscpbus1 drive 1: RRD40
> ra2 at mscpbus1 drive 2: RRD40
> rx0 at mscpbus1 drive 3: RX50
> qe0 at uba0 csr 174440 vec 500 ipl 17: delqa, address 08:00:2b:aa:bb:cc
> vscsi0 at root
> scsibus0 at vscsi0: 256 targets
> softraid0 at root
> scsibus1 at softraid0: 256 targets
> boot device: ra0
> disklabels not read: ra0 ra1 ra2 rx0
> root on ra0a swap on ra0b dump on ra0b
> panic: cannot open disk, 0x900/0x902, error 6
> Stopped at _dk_mountroot+0x53: ashl $4, r7, r5
> RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC!
> DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION!
> ddb> trace
> Stack traceback :
> _main+0x4e0(void)
> _start+0x5a6(0x3ad538)
> ddb> ps
> PID PPID PGRP UID S FLAGS WAIT COMMAND
> 5 0 0 0 3 0x100200 bored crypto
> 4 0 0 0 3 0x100200 pftm pfpurge
> 3 0 0 0 3 0x100200 rxonline syswq
> 2 0 0 0 3 0x40100200 idle0
> 1 0 0 0 3 0 initexec swapper
> * 0 -1 0 0 7 0x200 swapper
> ddb>
>
> any comments would be welcome.
>
> --yasuoka
[demime 1.01d removed an attachment of type APPLICATION/DEFANGED which had a name of BiggRanger.225DEFANGED-vcf]