On Jan 20, 2023, at 9:11 PM, Trent McNair <tmcnair%gmail.com@localhost> wrote:
>
> I commented out the kernel size check code and built a minimal kernel,
> it does boot and tries to go into single-user mode but only after a
> very long time . After that, things start crashing, complaining about
> swap space. I'm not sure at what point in the boot sequence the swap
> gets activated, but I don't see any indication on my NFS server that
> the swap file is mounted or accessed. I tried swapctl -A from the
> shell prompt but that crashed as well. I've attached a boot log below.
One thing I've done when booting minimal-memory systems (such as an HP 9000-332 with 8MB) is put attaching a swap file at the very top of /etc/rc, because I was seeing the attempt to execute rc failing due to lack of memory. Normally swap is attached towards the middle or end of /etc/rc, from what I recall anyway.
That's a very good point
% cd /etc/rc.d && rcorder * | head -20 | fmt
wdogctl fsck_root modules resize_root root devpubd-early devpubd
zfs ccd rndctl cgd lvm raidframe sysctl DISKS dkstrat swap1 fsck
mountcritlocal clearcritlocal
From a quick look at the rc startup order for NetBSD-10 the system runs a few things before swap1 gets called. swap2 comes much later (swap1 mounts swap devices, while swap2 mounts on files).
There is possibly an argument for a "swap0", to come directly after fsck_root, which would attempt to mount available swap devices, and swap1 could be tweaked to ignore existing device mounts
David