Hello,

I'm attempting to boot a 1.5.2 kernel over the network and while it
appears to be doing that, when it starts to run it dies with a VMEbus
exception. Here's the console output:

167-Bug>nbo
Network Booting from: VME167, Controller 0, Device 0
Loading: MVME167C

Client IP Address      = 192.168.100.6
Server IP Address      = 192.168.100.1
Gateway IP Address     = 0.0.0.0
Subnet IP Address Mask = 255.255.255.0
Boot File Name         = MVME167C
Argument File Name     =

Network Boot File load in progress... To abort hit <BREAK>

Bytes Received =&18996, Bytes Loaded =&18996
Bytes/Second   =&18996, Elapsed Time =1 Second(s)
>> BSD MVME167 netboot (via MVME167C) [$Revision: 1.2 $]
device: ie0 attached to 08:00:3e:21:07:e2
boot: client IP address: 192.168.100.6
boot: client name: malbolge
root addr=192.168.100.1 path=/home/diskless/malbolge/root
932440+33256+144948+[147540+136440]=0x154d6c
Start @ 0x0x8000 ...

Exception: Access Fault (Local Off Board)
PC =000081A4 SR =2700
Format/Vector =7008
SSW =0085 Fault Address =0F0E4000 Effective Address =000ECFFC
PC   =000081A4 SR   =2700=TR:OFF_S._7_....
VBR  =FFE00000 USP  =FFE10000 MSP  =FFE10000 ISP* =000ED000
SFC  =1=UD     DFC  =1=UD     CACR =00000000=D:._I:.
D0   =0F0E4000 D1   =1F0A8000 D2   =0015CD6C D3   =00000000
D4   =00000000 D5   =00000000 D6   =FFF46000 D7   =00000000
A0   =0F0E4004 A1   =FFFC1F31 A2   =0000843E A3   =003F40B8
A4   =00008000 A5   =00000000 A6   =003EFFA0 A7   =000ED000
000081A4 4298              CLR.L       (A0)+
167-Bug>

Booting from tape yields the same results.

I'm at a loss as to what to look at at this point. The J1 1-2
jumper is off, but this error occurs with it on as well. There
are no other boards in the chassis.

This board has 32MB of RAM which passed the diagnostic tests
and the ENV parameters are set to the defaults, except for the
"Network Auto Boot Config Param Pointer which is set to FFFC0200,
although the default for this value (0), didn't effect the
exception either.

Any suggestions ?

Thanks.
--
Mike Wlodarczyk