[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
can't boot mvme187
- To: bugs_(_at_)_openbsd_(_dot_)_org
- Subject: can't boot mvme187
- From: Dan Miller <danny_(_at_)_mtu_(_dot_)_edu>
- Date: Sun, 21 Dec 2003 15:23:54 -0500
I have a Motorola MVME187 currently running OpenBSD2.5. I have been
using it for several years.
I am trying to upgrade it to the current snapshot of OpenBSD 3.4 from
one of your mirror sites. I have a spare drive in my machine so I
loaded sdboot, bootxx, bsd, and bsd.rd into the spare drive and used
installboot to load the boot block for that drive. I then booted the
machine from that spare drive(/dev/sd2a) and here is what I get:
Copyright Motorola Inc. 1988 - 1994, All Rights Reserved
MVME187 Debugger/Diagnostics Release Version 2.3 - 12/16/94
COLD Start
Local Memory Found =04000000 (&67108864)
--Break Detected--
Autoboot in progress... To abort hit <BREAK>
--Break Detected--
1) Continue System Start Up
2) Select Alternate Boot Device
3) Go to System Debugger
4) Initiate Service Call
5) Display System Test Errors
6) Dump Memory to Tape
Enter Menu #: 3
187-Bug>BO 00 20
Booting from: VME187, Controller 0, Drive 20
Loading: Operating System
Volume: M88K
IPL loaded at: $009F0000
Boot: bug device: ctrl=0, dev=32
bootxx: first level bootstrap program [$Revision: 1.1 $]
/
OpenBSD/mvme88k bootsd [$Revision: 1.2 $]
1970176+139264+249216+[74712+89679]=0x267fab
Start @ 0x10020 ...
Controler Address @ fff47000 ...
CPU0 is attached with 2 MC88200 CMMUs
[ using 164391 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-2003 OpenBSD. All rights reserved. http://www.OpenBSD.org
OpenBSD 3.4-current (GENERIC) #285: Thu Dec 18 19:01:32 GMT 2003
root_(_at_)_arzon_(_dot_)_gentiane_(_dot_)_org:/usr/src/sys/arch/mvme88k/compile/GENERIC
real mem = 67108864
avail mem = 59092992 (14427 pages)
using 844 buffers containing 3457024 bytes of memory
mainbus0 (root): Motorola MVME187, 25MHz
cpu0: M88100 rev 0x3, 2 CMMU
cpu0: M88200 (16K) rev 0x9, global Icache, M88200 (16K) rev 0x9, global Dcache
bugtty0 at mainbus0 addr 0xfff45000: fallback console
pcctwo0 at mainbus0 addr 0xfff00000: rev 0
clock0 at pcctwo0 ipl 5
memc0 at pcctwo0 offset 0x43000: MCECC rev 0
memc1 at pcctwo0 offset 0x43100: MCECC rev 0
nvram0 at pcctwo0 offset 0xc0000: MK48T08 len 8192
cl0 at pcctwo0 offset 0x45000 ipl 3 console
ssh0 at pcctwo0 offset 0x47000 ipl 2: version 2 target 7
scsibus0 at ssh0: 8 targets
ssh0: target 0 now synchronous, period=100ns, offset=8
probe(ssh0:0:0): Sense Error Code 0
sd0 at scsibus0 targ 0 lun 0: <FUJITSU, M2624F-512, M403> SCSI1 0/direct fixed
sd0: 496MB, 1429 cyl, 11 head, 64 sec, 512 bytes/sec, 1015812 sec total
ssh0: target 2 now synchronous, period=100ns, offset=8
sd1 at scsibus0 targ 2 lun 0: <FUJITSU, M2624F-512, M404> SCSI1 0/direct fixed
sd1: 496MB, 1429 cyl, 11 head, 64 sec, 512 bytes/sec, 1015812 sec total
ssh0: target 3 rejected sync request
cd0 at scsibus0 targ 3 lun 0: <TOSHIBA, CD-ROM XM-3301TA, 2342> SCSI2
5/cdrom re
movable
ssh0: target 4 rejected sync request
st0 at scsibus0 targ 4 lun 0: <ARCHIVE, VIPER 150 21247, -011> SCSI1
1/sequentia
l removable
st0: rogue, drive empty
vme0 at pcctwo0 offset 0x40000: vector base 0x80, system controller
vme0: using BUG parameters
vme0: 1phys 0x04000000-0xefff0000 to VME 0x04000000-0xefff0000
vme0: 2phys 0xff000000-0xff7f0000 to VME 0xff000000-0xff7f0000
vme0: 3phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
vme0: 4phys 0x00000000-0x00000000 to VME 0x00000000-0x00000000
vme0: vme to cpu irq level 1:1
vmes0 at vme0
vx0 at vmes0 addr 0xff780000 vaddr 0x5526000 vec 0x80 ipl 3
Data access fault (Bus Error) v = 1d2804, frame eee07770
R00-05: 0x00000000 0x001ea240 0x05526118 0x00000000 0x0000000c 0x001d2810
R06-11: 0x001d2804 0x0022e558 0x001e855e 0x41000000 0x000007ab 0x00000006
R12-17: 0x00000000 0x05526000 0x00000000 0x00000000 0x00000000 0x00000000
R18-23: 0x00000000 0xeee079b8 0x00212d68 0x001c8098 0x003e7780 0x003e0800
R24-29: 0x00000000 0x05526118 0x00000000 0x00000000 0x00000000 0x00000000
R30-31: 0x00000000 0xeee07870
sxip 1d2806 snip 1d280a sfip 1d280e
dmt0 403f dmd0 0 dma0 5526120
dmt1 0 dmd1 0 dma1 5526120
dmt2 0 dmd2 0 dma2 5526120
fault type 3
[DMT0=403f: st.s 0 to 5526120 as 15 not double not xmem]
fpsr eee079b8 fpcr 212d68 epsr a00003f2 ssbr 1e855c
fpecr 0 fphs1 ffffffff fpls1 ffffffff fphs2 0 fpls2 0
fppt 1 fprh 62da8 fprl eee078d0 fpit 69fd8
vector 3 mask 6 mode 100 scratch1 1cefbc cpu 0
panic: Data Access Exception
Stopped at _Debugger: tb0 0x0, r0 ,0x84
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 base = 0xeee075e8
(0) _Debugger(stackless)
(1) _panic+0x110
(2)?0xeee07678
ddb> ps
PID PPID PGRP UID S FLAGS WAIT COMMAND
* 0 -1 0 0 2 0x80204 swapper
ddb>
It looks like this kernel doesn't like device vx0, whatever that is??
Visit your host, monkey.org