From owner-freebsd-current Fri May 24 18:08:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25085 for current-outgoing; Fri, 24 May 1996 18:08:29 -0700 (PDT) Received: from relay-2.mail.demon.net (disperse.demon.co.uk [158.152.1.77]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA25080 for ; Fri, 24 May 1996 18:08:24 -0700 (PDT) Received: from post.demon.co.uk ([158.152.1.72]) by relay-2.mail.demon.net id ae13948; 25 May 96 1:32 +0100 Received: from jraynard.demon.co.uk ([158.152.42.77]) by relay-3.mail.demon.net id aa14014; 25 May 96 1:26 +0100 Received: (from fcurrent@localhost) by jraynard.demon.co.uk (8.7.5/8.6.12) id WAA16934; Fri, 24 May 1996 22:35:28 GMT Date: Fri, 24 May 1996 22:35:28 GMT Message-Id: <199605242235.WAA16934@jraynard.demon.co.uk> From: James Raynard To: coredump@nervosa.com CC: current@freebsd.org, toor@dyson.iquest.net In-reply-to: (coredump@nervosa.com) Subject: Re: Possible problem with new VM code? Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Look in your logfiles to see if the kernel reported a "swap_pager: out of > swap space." If this is the case, you need to increase your swap size. Nope, that's not the problem. Every now and again something dies with a SIGBUS or a SIGSEGV, even if I have 30 or 40M of swap free. Sorry if I didn't make that very clear. -- James Raynard, Edinburgh, Scotland jraynard@dial.pipex.com james@jraynard.demon.co.uk