Subject: Re: MVME-167 network boot problem
To: Wlodarczyk, Mike <MikeWl@CONDORSYS.com>
From: Steve Woodford <firstname.lastname@example.org>
Date: 02/05/2002 10:00:36
On Mon, 4 Feb 2002, Wlodarczyk, Mike wrote:
> 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:
From the 167-Bug> prompt:
167-Bug> mm fffc0000 ;l
fffc0000: xxxxxxxx? 0 <-- you type 0
fffc0004: xxxxxxxx? 0 <-- you type 0
fffc0008: xxxxxxxx? . <-- you type .
This problem is on my ToDo list already. Basically, the startup code
blindly believes what it reads from NVRAM wrt the start address and length
of offboard memory (eg. VMEbus RAM cards).
I need to implement some form of checksum/crc validation of nvram before
believing the contents.