Re: Removing options MIPS3 cause DS5000 to loop during boot

[Erik Bertelsen <bertelsen.erik%gmail.com@localhost>]

Sorry to follow up to myself.

>  diff S4 S5
> 30d29
> < options       MIPS3           # R4000/R4400 CPUs
>
> then the machine boots to the point of starting init and then hangs
> solidly -- the only recovery seems to power cycle the machine.
>

Observing that neither DEBUG nor DIAGNOSTIC were enabled, I tried to add them:

 diff S5 S6
40,41c40,41
< #options      DIAGNOSTIC              # extra kernel debugging checks
< #options      DEBUG                   # extra kernel debugging support
---
> options       DIAGNOSTIC              # extra kernel debugging checks
> options       DEBUG                   # extra kernel debugging support

Booting the S6 kernel actually produces an error message rather than
just hanging:

Boot: 3/rz4/netbsd.s6
3455120+143648 [192336+187118]=0x3cb904
Starting at 0x80030000

mips_fixup_stubs: 6768 fixups done in 0 cycles
Loaded initial symtab at 0x8039e9b0, strtab at 0x803cde14, # entries 12000
mcclock: iters 11680 computed MHz 33, instrs per usec=19
segment  0 start 00000000 size 02000000
phys segment: 0x2000000 @ 0
adding 0x402000 @ 0x3fe000 to freelist 1
adding 0x1800000 @ 0x800000 to freelist 0
pmap_steal_memory: seg 0: 0x3fe 0x3fe 0x800 0x800
pmap_steal_memory: seg 0: 0x424 0x424 0x800 0x800
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.99.49 (S6) #0: Thu Apr 21 17:47:27 CEST 2011
        
erik%x8-nb.h.recerik.dk@localhost:/home/NetBSD/crossbuild/obj.pmax/sys/arch/pmax/compile/S6
DECstation 5000/133 (3MIN)
total memory = 32768 KB
avail memory = 27884 KB
mainbus0 (root)
cpu0 at mainbus0: MIPS R3000A CPU (0x230) Rev. 3.0 with MIPS R3010 FPC Rev. 4.0
cpu0: 64KB/4B direct-mapped Instruction cache, 64 TLB entries
cpu0: 128KB/4B direct-mapped write-through Data cache
tc0 at mainbus0: 12.5 MHz clock
ioasic0 at tc0 slot 3 offset 0x0
le0 at ioasic0 offset 0xc0000: address 08:00:2b:32:56:6f
le0: 32 receive buffers, 8 transmit buffers
3MIN: imask 1030, enabling slot 0x2, dev 0xc362ac18 handler 0x80033280
zsc0 at ioasic0 offset 0x100000
vsms0 at zsc0 channel 0
wsmouse0 at vsms0 mux 0
zstty0 at zsc0 channel 1
3MIN: imask 1130, enabling slot 0x0, dev 0xc362ac18 handler 0x802fef4c
zsc1 at ioasic0 offset 0x180000
lkkbd0 at zsc1 channel 0
wskbd0 at lkkbd0 mux 1
zstty1 at zsc1 channel 1 (console i/o)
3MIN: imask 1170, enabling slot 0x1, dev 0xc362ac18 handler 0x802fef4c
mcclock0 at ioasic0 offset 0x200000: mc146818 or compatible
asc0 at ioasic0 offset 0x3000003MIN: imask 11f0, enabling slot 0x3,
dev 0xc362ac18 handler 0x80183270
: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at asc0: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 4 lun 0: <QUANTUM, QM39100TD-S, N1B0> disk fixed
sd0: 8683 MB, 8057 cyl, 10 head, 220 sec, 512 bytes/sect x 17783249 sectors
sd0: sync (200.00ns offset 15), 8-bit (5.000MB/s) transfers, tagged queueing
boot device: sd0
root on sd0a dumps on sd0b
mountroot: trying nfs...
mountroot: trying lfs...
mountroot: trying ffs...
root file system type: ffs
init: copying out flags `-s' 3
init: copying out path `/sbin/init' 11
pid 1(init): ABI set to O32 (e_flags=0x1007)
pid 1(init): trap: cpu0, TLB miss (load or instr. fetch) in kernel mode
status=0x20080014, cause=0x30000008, epc=0x80125a3c, vaddr=0xff00
tf=0xc3e7fa90 ksp=0xc3e7fb30 ra=0x801d4db4 ppl=0x81ee5e44
kernel: TLB miss (load or instr. fetch) trap
Stopped in pid 1.1 (init) at    netbsd:mutex_abort:     lw      v1,0(a0)
db> t
0xc3e7fb30: mutex_abort+0 (ff00,80329ca0,80344378,8036dc50) ra 801d4db4 sz 0
0xc3e7fb30: pmap_page_protect+d4 (ff00,80329ca0,80344378,8036dc50) ra 802a3b50 s
z 48
0xc3e7fb60: uvm_anfree+18c (ff00,80329ca0,80344378,8036dc50) ra 802a1a20 sz 32
0xc3e7fb80: amap_wipeout+140 (ff00,80329ca0,80344378,8036dc50) ra 802b5504 sz 40

0xc3e7fba8: uvm_unmap_detach+74 (ff00,80329ca0,80344378,8036dc50) ra 802b563c sz
 40
0xc3e7fbd0: uvm_unmap1+8c (ff00,80329ca0,80344378,8036dc50) ra 802b58c4 sz 64
0xc3e7fc10: uvmspace_exec+d8 (ff00,80329ca0,80344378,8036dc50) ra 80116674 sz 40

0xc3e7fc38: execve1+7b0 (ff00,7fff7ff2,7fff7fe4,0) ra 80117460 sz 512
0xc3e7fe38: sys_execve+28 (ff00,7fff7ff2,7fff7fe4,0) ra 800c51b8 sz 32
0xc3e7fe58: start_init+39c (81f0b340,7fff7ff2,7fff7fe4,0) ra 8017745c sz 240
0xc3e7ff48: mips1_lwp_trampoline+18 (81f0b340,7fff7ff2,7fff7fe4,0) ra 0 sz 24
User-level: pid 1.1
db>


I hope that this makes it easier for one of the mips gurus to
determine the cause of failure.

- Erik