Subject: Re: 1.4 pmax buglets?
To: Jonathan Stone <jonathan@DSG.Stanford.EDU>
From: Simon Burge <>
List: port-pmax
Date: 04/20/1999 10:27:09
Jonathan Stone wrote:

> hi all,
> I confess I've lost track.   where is the pmax port currently at with:
>     * VM kernel-address space allocation (crashes due to
>          not allocating enough space, now that the space for the
> 	 mbuf pool we dont use is no longer allocated)

People are still getting the problem - Tracy J. Di Marco White got a
"panic: uvm_km_suballoc: unable to allocate space in parent map" on a 3
day old 1.4_ALPHA kernel.  I've not seen the problem at all on machines
with 24MB, 32MB, 96MB and 128MB of RAM...

>     * bswap{16,32} and .abicalls  for libsa/libkern?
>       (the .abicalls are supposed to be protected by an ifdef
>       which  standalone/kernel code is supposed to turn on)

Stand-alone stuff (bootblocks) builds ok.  On the 1.4 branch, the kernel
compiles cleanly, but I've just noticed that -current breaks because
-DABICALLS to passed to ${CC} for all the .S files and thus generates
PIC code and the kernel link fails.  It looks like the simplest fix is
to remove the ABICALL dance from libkern/byte_swap_?.S.  In fact I've
just doing this now, so that at least -current kernel compiles work
again.  (Well, I tell a lie - our ssh gateway seems dead at the moment.)

This all gets back to <> _unconditionally_ adding "-DPIC
-DABICALLS" to AINC.  I posted something to tech-toolchain about this
a month ago suggesting that we protect that addition with a check on a
conditional like "MIPS_NO_PIC_MODE" but didn't get anywhere...

>     * /dev/rnd random-number support

"Works for me" I think.  I get random gibberish when I access the
device, which I think is the point :-)

Another question - should the INSTALL kernel have the NFS_BOOT_BOOTP and
NFS_BOOT_DHCP options?  I can't get netboots to work without them...