From owner-freebsd-current Wed May 23 1:10:35 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 78E9637B61A; Wed, 23 May 2001 01:10:29 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id SAA01535; Wed, 23 May 2001 18:10:19 +1000 Date: Wed, 23 May 2001 18:08:51 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Peter Wemm Cc: John Baldwin , current@FreeBSD.ORG, Alfred Perlstein Subject: Re: HEADS UP: I broke swapping In-Reply-To: <20010523014814.4A2E2380A@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Tue, 22 May 2001, Peter Wemm wrote: > 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. des's adsp.c test program caused this here on a machine with 64MB RAM and 132MB swap. No progress was made killing `bigproc' because everything gets stuck on "vmwait". It is hard to see where the get stuck because the "vmwait" label is far from unique. It is used in both the vm_wait() and the vm_await() functions which are called from all over. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message