From owner-freebsd-current Tue May 22 18:48:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 74E6037B424; Tue, 22 May 2001 18:48:14 -0700 (PDT) (envelope-from peter@wemm.org) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f4N1mEM85088; Tue, 22 May 2001 18:48:14 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 4A2E2380A; Tue, 22 May 2001 18:48:14 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: John Baldwin Cc: current@FreeBSD.ORG, Alfred Perlstein Subject: Re: HEADS UP: I broke swapping In-Reply-To: Date: Tue, 22 May 2001 18:48:14 -0700 From: Peter Wemm Message-Id: <20010523014814.4A2E2380A@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > If I have swap (i.e. I've run swapon on a swap partition) the program is kill ed > by the system fine. If I don't have swap, then both the memkill process adn > the swapper process (proc0) are stuck in the "vmwait" wait channel used by > VM_WAIT. Any ideas? This may not be a new problem. I have seen a lot of machines hit this sort of thing at work. It can end up in the majority of processes on the system in this state. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message