Subject: Re: scheduler: no room for pid xx(.....), free x
To: Dave Huang <email@example.com>
From: Tom Ivar Helbekkmo <firstname.lastname@example.org>
Date: 12/29/1998 11:40:36
Dave Huang <email@example.com> writes:
> Dec 23 23:58:06 fluff /netbsd: : no room for pid 123(cron), free 1
I've seen this recently, too, on a VAX running -current. I was doing
memory intensive work at the time, in an NFS-mounted file system, but
had plenty local swap space available. Unlike yourself, I was not
able to keep the system running: it seemingly immediately lost control
of its whole VM system, generating kernel page faults and complaints
of physical memory (parity) errors (which the machine in question does
not have; extensive testing shows it to be OK, and it runs 1.3F rock
solid). This is probably a VAX-specific bug, triggered by the problem
that led to the "no room" message.
Popularity is the hallmark of mediocrity. --Niles Crane, "Frasier"