Subject: Re: panic: uvm_km_suballoc: unable to allocate space in parent map
To: None <port-pmax@netbsd.org>
From: Michael L. Hitch <mhitch@lightning.oscs.montana.edu>
List: port-pmax
Date: 12/14/1998 21:34:43
On Tue, 15 Dec 1998, Simon Burge wrote:

> On Mon, 14 Dec 1998 23:20:56 +0100 (GMT)  Thorsten Frueauf wrote:
> 
> > I got a DECstation 5000/200 and I bootstrapped it with the NetBSD 1.3.3
> > snapshot provided by Simon (thanx for doing this!) - worked fine so far.
> > So I wanted to bring it up to current and mounted src supped from
> > 29.11.1998 and compiled a kernel. But if I try booting it, I get the
    ^^^^^^^^^^

> Try the kernel in ftp.netbsd.org:/pub/NetBSD/misc/simonb/kernel-19981208.
> It's a -current kernel as of about the 8th of December.  It's a GENERIC
> kernel without the slip and ppp drivers, and COMPAT_1{0,1} enabled.
> 
> There were some problems fixed recently to do with large swap partitions,
> but you shouldn't have seen that particular problem until swapctl was
> run in /etc/rc.

  I think the changes for the memory allocation was done December 5, and
that adjusted the size of the kernel PTE table and also the size of the
kernel virtual memory available.  Those changes might help, depending upon
which submap the error is occuring in.  A stack backtrace (if available)
would give me a better idea of which memory allocation was failing.
I was trying to understand the various types of memory allocation that
was going on during that part of the kernel startup, hoping that I could
figure out a better way to determine the kernel PTE size.

Michael