Date: Thu, 14 May 1998 13:18:56 +0200 From: Eivind Eklund <eivind@yes.no> To: Terry Lambert <tlambert@primenet.com>, Alexander Litvin <archer@lucky.net> Cc: current@FreeBSD.ORG Subject: Re: daemons exiting on signal 11 Message-ID: <19980514131856.48680@follo.net> In-Reply-To: <199805140302.UAA04302@usr08.primenet.com>; from Terry Lambert on Thu, May 14, 1998 at 03:02:08AM %2B0000 References: <19980513093110.21002@carrier.kiev.ua> <199805140302.UAA04302@usr08.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 14, 1998 at 03:02:08AM +0000, Terry Lambert wrote: > > I thought the problem has gone. But yesterday trying to test > > new softupdates patches, I loaded my machine with 'make -j64 > > buildworld', and at some point cron started to exit with SIGSEGV. > > After makeworld finished problem with cron didn't disappear, > > so I needed to restart cron :-\ > > For readers who might have been alarmed by this: > > Note that this is not indicative of a problem in the soft updates > code. This means that he was out of swap + RAM, and when cron > went to get a page, it was denied, and could not continue to run. The part about the it not having to do with soft updates is correct. The rest is slightly misleading - there is a problem in the VM code (has been there for a few weeks) which is triggered when you run out of memory and swap. After you've been out of memory, the new forks of daemons die with SIGSEGV (seemingly right after the fork - at least before they get anything done). This is not just while you're out of memory - it behaviour continues until you restart the daemons. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980514131856.48680>