Subject: savecore problem fixed
To: None <woods@planix.com>
From: Gordon W. Ross <gwr@mc.com>
List: port-sun3
Date: 11/25/1997 17:38:54
> Date: Tue, 25 Nov 1997 09:53:22 -0500
> From: "Gordon W. Ross" <gwr@bach>
> 
> > Which brings up the issue of how much bigger the dump device must be
> > than physical RAM.  I've got 48KB of space on the primary dump/swap

Need:  dump_device_size >= (physmem + 32KB)

> > device now for a 32MB machine, but I've seen the "WARNING: EOF on dump"
> > from savecore and now that I've peered at the source the only way I can
> > see that it could do that is if the dumpsize values got trashed in the
> > crash or were miscalculated in the first place (unless I've seriously
> > under-calculated the extra space required for a dump).
> 
> Probably just a bug somewhere.  The sun3 uses three extra pages.
> I just tried it out, and this machine that used to be able to
> savecore now complains about "EOF on dump device" like yours.
> Nonetheless, the kernel core file appears to be usable.

The problem was that I misunderstood the meaning of the dumpsize
variable in the kernel.  It is the size of just the raw memory part
of the dump, not the entire dump imgage.  (Who woulda guessed?)

It's fixed now.