> 
> Well, okay, this _is_ the latest :-)
> It gets much further than the previous kernel, but it still panics
> at another point.

Since the kernel seems to be panicing in part of the vfs initialization
(which should be quite stable code, AFAIK), I think you have a weird
problem.  The best solution I've seen to these is to make clean and
make again.

Have you changed the config recently w/o a make clean?

I had some similar goofyness which went away with a make clean.

Take care & good luck,

Bill

> Here goes the boot log:
> 
> NetBSD/mac68k console
[snip ok stuff]
> fpu0 at mainbus0 (emulator)
> vm_fault(158000, 31a3f000, 3, 0) -> 1
>   type 8, code [mmu,,ssw]: 485
> trap type 8, code = 485, v= 31a3ff3c
> kernel: MMU fault trap
> pid = 0, pc = 0003A206, ps = 2000, sfc = 0001, dfc = 0001
> Registers:
>              0        1        2        3        4        5        6        7
> dreg: 4AB9000F 00000000 00898000 FFFFD000 0014F2F0 F9001000 00000000 00000002
> areg: 00002E2C 00000010 06BFFF00 00000858 0014F1C4 00B06AC8 00151F58 FFFFCFFC
> 
> Kernel stack (00151E84):
[snip went the stack]
> panic: MMU fault
> Stopped at      _Debugger+0x6:  unlk    a6
> db> t
> _Debugger(8,151ebc,d4462,d40ff,898000) + 6
> _panic(d40ff,898000,ffffd000,14f2f0,f9001000) + 40
> _trap(8,485,31a3ff3c) + 1e6
> _addrerr(?)
> _vfs_opv_init_explicit(858) + e8
> _vfs_opv_init(ffffcffc,151fac,1c102,154147,c0a0) + 14
> _vfsinit(154147,c0a0,8001078a,f9001000,ffffcffc) + 14
> _main() + 2c4
> _main() + 2c4
> db> 

Weird. Am I mis-reading something? vfs_opv_init takes void, not
something with 5 parameters. :-( And its code looks like it should be
more than 20 (0x14) bytes long, so it's not a symbol slip. Also,
vfs_opv_init_explicit takes a pointer to a data table (in the data
segment?). Is 0x858 a reasonable pointer?

It looks like a bad link. make clean tens to make it better. Sorry.

Take care,

Bill